Sharing your CloudCannon Sites allows you to provide everyone on your team with access to your content. You can configure which resources they have access to, what actions they can perform, and how they log in to CloudCannon.
Articles in this section are helpful for developers responsible for configuring access to CloudCannon.
In the Sharing section of our Developer documentation, we cover:
- Custom Permission Groups — Learn how to create your own Permission Groups and specify which resources Group members can access
- Site Sharing — Learn how to give an Organization Member permission to access a specific Site in your Organization
- Guest Access — Learn how to create a site-specific password to share your content with people outside of CloudCannon
- SSO/SAML — Learn how to set up Single Sign-On for greater security
- Multi-factor Authentication — Learn how to add an extra layer of security to your account and require MFA for Organization members
Let’s briefly introduce a few of these topics.
Custom Permission Groups#
This feature is available on our Team and Enterprise plans.
CloudCannon provides Default Permission Groups for every Organization A workspace in CloudCannon that groups together Sites, Organization Members, and shared resources. It is also the unit CloudCannon bills for. You can define permissions for your Organization, controlling the access each Organization Member has to resources on CloudCannon. You can create and be a part of multiple Organizations. A user-defined set of permissions and access controls in CloudCannon that can be assigned to Organization Members. Custom Permission Groups allow fine-grained control over what users can see and do within your Organization.Organization
Custom Permission Group
For a more in-depth explanation of Custom Permission Groups, please read our documentation:
- What are Custom Permission Groups?
- Create a Custom Permission Group
- Delete a Custom Permission Group
- Edit a Custom Permission Group
- Best practices for Custom Permission Groups
Site Sharing#
You can share a specific Site with collaborators from outside your CloudCannon Organization without giving them access to all your Sites. There are two Default Permission Groups for Site Sharing, equivalent to the Technical Editors and Editors groups.
For a more in-depth explanation of Site Sharing, please read our documentation:
- Add an Organization Member to Site Sharing
- Remove an Organization Member from Site Sharing
- Edit an Organization Member's Site Sharing Permission Group
Guest Access#
You can share a specific Site with collaborators who do not have CloudCannon accounts and configure a simplified Site interface for them. Guests can log in using a Site-specific password and make changes to your content.
For a more in-depth explanation of Guest Access, please read our documentation:
- Turn on Guest Access for a Site
- Configure the commit details for Guests
- Customize the Guest Permission Group
- Configure the Guest Login Page
- Configure the Guest Dashboard support links
SSO/SAML#
This feature is available on our Enterprise plans.
CloudCannon supports Single Sign-On An abbreviation of Single Sign-On/Security Assertion Markup Language, SSO/SAML is an authentication method that allows users to access multiple applications with a single set of credentials. CloudCannon supports SSO/SAML for Enterprise Plan customers. With SSO/SAML, rather than logging in to CloudCannon directly, CloudCannon authenticates the user's identity using their Identity Provider software.SSO/SAML
For a more in-depth explanation of SSO/SAML, please read our documentation:
- What is SSO/SAML?
- Add SSO/SAML authentication
- Edit SSO/SAML authentication
- Remove SSO/SAML authentication
Multi-factor Authentication#
Multi-factor Authentication (MFA) adds a second factor to your login process, typically a code from an authenticator app. This helps protect your account even if your password is compromised. Organization Owners can optionally require MFA for all Organization Members.
For a more in-depth explanation of Multi-factor Authentication, please read our documentation: