Migrating to Confluence cloud and have a couple questions.

Dave Hattig

We have the need for customers outside our Org. to login with there own credentials and not use SSO. Is that a possibility?

We would like each client to be able to have their own pages and have large files attached to those pages. I have heard the file size should stay to 10MB but have heard adjusting to 100MB is ok. Is that actually ok or would it dramatically affect performance?

If we create a space with multiple pages. Add permissions for clients access. Do clients have visibility to see other clients that have access? Or would other user access be hidden?

What is the best way for a client outside our org to access their page/s? Can links be added to the service center that are only accessible to certain clients? 

 

Thank you in advance for any help provided!!

Mikael Sandberg

Yes, it is possible to use accounts that are not using SSO, you can even have a mix of it. We for example are managing all our accounts via Okta, but we do have customers accessing our instance that is not using SSO to get to Confluence.

The file size is more based on what plan you are on, it is only Premium and above that have unlimited storage. So bumping up the file size should be fine.

Yes, your customers will see other customers if they have access to the same space. Atlassian is working on a External collaboration feature that will be available later this year, and from what I have heard this will limit what the external collaborator will see.

There are a couple of options for this, for example you could use Scroll Viewport which allows you to create global URL redirects for your customers. Any Confluence pages added to your JSM projects will honor the permissions in Confluence, so if a user do not have permission to a specific page, it will not be visible from JSM.