Allowing internal users access irrespective of IP allowlisting

[Anna Dziubańska]

We have subscribed to Confluence Premium to be able to use the IP allowlisting functionality.

Our scenario is that 90% of Confluence is used for internal purposes and access should be allowed for our internal users based on their account permissions (all internal users have individual Confluence accounts).

The remaining 10% of our Confluence use (a single space) is dedicated to client facing documentation, which we want to enable on a read-only basis to our customer base (but not to the whole internet). The clients shouldn't need a Confluence account, access to the client facing Space will be managed with IP allowlisting.

We have tested the space permissions settings and managed to configure the required client-facing space to be visible to allowlisted customers without confluence account, however, now our internal users (with confluence accounts) also need to access all internal spaces from an allowlisted IP.

We would like to avoid forcing our internal users to connect from allowlisted IPs - is it possible to set this up in a way that a logged in user can access Confluence from any IP?

[Cassie the Jira Mechanic]

Yes, you could use Confluence Guests. Atlassian has a nice how to document already so I will link you to that:

Invite guests to Confluence | Confluence Cloud | Atlassian Support

[Anna Dziubańska]

thanks Cassie. This could work, if the limitation of 5 guests per paid user wasn't there. We would also prepare not having to force the clients to create an account, but have the contents available with the click of a button.

I was looking to see if there is a possibility for the internal users to skip over the IP requirement (i.e. IP requirement for anonymous users, no IP requirement for logged in users)