Experience the difference of "Elite".

Custom CSS for Owner Portal

Status: Requested 1 Vote
Cole W
May 30, 2022 12:49 AM
Joined Sep, 2021 8 posts

We just added the PM add-on so our owners can have a portal to log in to to check how their properties are going. Unfortunately, I discovered that the portal looks very offbrand to us. We'd love to have the opportunity to white label the portal more to match our brand. And especially to have the logo on the logged in application not be OwnerRez. Its a marketing point for us to have this, but its value is diminished when it doesn't look like our own product. I might have to build out my own owner portal if this isn't possible.

Ken T
May 30, 2022 3:25 PM
OR Team Member Joined Aug, 2019 787 posts

We just added what I think is what you're looking for:

https://www.ownerreservations.com/support/articles/portal-going-live

Cole W
May 30, 2022 3:29 PM
Joined Sep, 2021 8 posts

No, I'm sorry. This isn't what I'm asking for. This is hosted through my domain but it is not branded to us. For instance, the logo when logged in is OwnerRez, even though it's our logo at the login screen. And the colors throughout the logged in area are OwnerRez, not our brand color. We would like to control the CSS for our portal. 

Chris Hynes
May 30, 2022 5:46 PM
OR Team Member Joined Oct, 2012 1353 posts

One thing I notice is that you've got the CNAME configured correctly, on your portal DNS but you've also got some A records with non-OwnerRez IP addresses configured. Remove those to make sure that you're hitting the portal correctly.

Then log in using your portal URL (logging in via the normal OwnerRez login won't go to the branded portal).

If you're still seeing an OwnerRez logo, send a screenshot of your browser including the URL bar to help@ownerreservations.com and we'll have a look.

 

Cole W
May 30, 2022 7:10 PM
Joined Sep, 2021 8 posts

I'm sorry, but asking me to remove my A records for this domain isn't an acceptable ask. The A records I have configured I need, and also have nothing to do with the subdomain I configure for you. Nor should it interfere with your ability to retrieve my logo to use post authentication, considering that that logo is stored on your server side (since I had to upload it) and therefore any domain resolving for the image URL should point towards a domain you host (which it does).

Additionally, I don't think you're fully understanding my ask. I'm not saying that its not working. It is working. I just don't like how this feature is implemented. Because I don't have the option to use CUSTOM CSS for the whitelabeling. In order to properly white label it, I need more control over how the pages are rendered. For instance, on the authentication screen, you use green buttons. That is off brand for me. The fonts are different. The toolbar and text color is different. It makes this look like a sloppy implementation on our side.

I appreciate having this functionality. I'm just asking for you guys to take the next iteration of it.

Chris Hynes
May 30, 2022 8:09 PM
OR Team Member Joined Oct, 2012 1353 posts

I'm not suggesting you remove A records for your main domain, but you do need to remove them for the subdomain or resolution will go sometimes to OwnerRez and other times to the IP addresses in your subdomain A records.

You're correct, we don't currently support customizing the fonts colors on your branded portal subdomain. Good idea for an additional feature!

We do support the logo and I'm not able to reproduce your issue with the OwnerRez logo showing on your branded portal subdomain. If you're still having an issue with that, contact support with a detailed screenshot so we can drill in further.

Cole W
May 30, 2022 8:39 PM
Joined Sep, 2021 8 posts

Those A domains are the resolved IP addresses for your CNAME:

 ~ % dig portal.vacayzenvillas.com +all  




; <<>> DiG 9.10.6 <<>> portal.vacayzenvillas.com +all

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64534

;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1




;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 1232

;; QUESTION SECTION:

;portal.vacayzenvillas.com. IN A




;; ANSWER SECTION:

portal.vacayzenvillas.com. 3600 IN CNAME portal.ownerrez.com.

portal.ownerrez.com. 60 IN A 50.19.237.67

portal.ownerrez.com. 60 IN A 44.199.56.49




;; Query time: 149 msec

;; SERVER: 192.168.50.6#53(192.168.50.6)

;; WHEN: Mon May 30 20:20:31 EDT 2022

;; MSG SIZE  rcvd: 116




~ % dig portal.ownerrez.com

; <<>> DiG 9.10.6 <<>> portal.ownerrez.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27076

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1




;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 4096

;; QUESTION SECTION:

;portal.ownerrez.com. IN A




;; ANSWER SECTION:

portal.ownerrez.com. 51 IN A 44.199.56.49

portal.ownerrez.com. 51 IN A 50.19.237.67




;; Query time: 6 msec


However, directly querying the authoritative DNS shows that there aren't A records there:

% dig @ns-cloud-a1.googledomains.com portal.vacayzenvillas.com



; <<>> DiG 9.10.6 <<>> @ns-cloud-a1.googledomains.com portal.vacayzenvillas.com

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8087

;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; WARNING: recursion requested but not available



;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;portal.vacayzenvillas.com. IN A



;; ANSWER SECTION:

portal.vacayzenvillas.com. 3600 IN CNAME portal.ownerrez.com.



;; Query time: 39 msec

;; SERVER: 216.239.32.106#53(216.239.32.106)

;; WHEN: Mon May 30 20:29:25 EDT 2022

;; MSG SIZE  rcvd: 84

Meaning that for both my initial queries and the ones you ran, one of the resolvers in the chain is caching the CNAME records into A records. But this isn't an issue as they resolve correctly anyway. But I wanted to point that out if it comes up again.

I can confirm that my logo is now showing in the owner portal. However, it highlights why having custom CSS is so important. Our logo is simple high contrast. If I go white on black, I have a large black logo on the login screen against your white background which looks bad. If I go black on white, now I have an ugly white logo on the toolbar that doesn't match your dark gray toolbar. If I had CSS I could adjust it to my needs.