Before enabling domain verification, can Atlassian answer the question of, are there any restrictions inherent in this, for example?:
-Can you still access a "Domain verified" Confluence Cloud instance from outside the domain?
-Use Confluence Mobile to access the "Domain verified" Confluence Cloud instance from outside the domain?
-Change a password or edit accounts for a "Domain verified" Confluence Cloud instance from outside the domain?
-Any other restrictions?
Hi Allan,
I hope this is clear, but let me know if you have any questions?
Kind Regards,
Shannon
Shannon,
Thank you for your reply, but I'm not sure *I* was clear.
If user "jdoe@mycompany.com" has an account on an Atlassian cloud instance at "example1.atlassian.net," jdoe can access example1.atlassian.net from any location with internet access (work, home, school, public wi-fi, etc...).
If user "jdoe@mycompany.com" has an account on an Atlassian cloud instance at "example1.atlassian.net" with a verified domain "mycompany," can user jdoe still:
-Access the cloud instance from anywhere?
-Access the cloud instance with Confluence Mobile from anywhere?
-Administer user accounts from anywhere?
Or does jdoe need to access the cloud instance from within the verified domain?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Allan,
The verified domain doesn't control where you can access the instance.
If this is something you want to be able to control then I would recommend that you vote on this issue, which asks that administrators are able to control an IP whitelist of the IP addresses that can access the domain:
Let me know if you have any questions about that.
Kind Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.