Managing permissions in workspaces (Collaborators).
The Workspaces system is the official and secure way to allow third parties to collaborate on managing your applications, eliminating the need to share your main account's login credentials.
Below, we detail how to configure your workspace, add applications, manage invitations, and structure your team's permissions.
📌 1. Prerequisites
- Standard plan or higher: Creating workspaces and the ability to invite collaborators are exclusive features for Standard plan subscribers or higher.
- Active accounts: Both the workspace owner and the invited collaborators must have individual, active accounts registered on Square Cloud.
🏗️ 2. How to Create and Configure a Workspace
Only the resource owner can create the workspace and allocate applications to it.
Creating the Workspace:
- Access your dashboard.
- Click your profile icon and select the "Create a Workspace" option.
- Set an identification name for the workspace and confirm its creation.
Adding Applications to the Workspace:
- Navigate to your newly created Workspace dashboard.
- Click the "Add new" button.
- Select from the list which applications will be part of this scope of work.
Attention: Only the workspace owner has technical permission to add or remove applications from the workspace.
🤝 3. How Do I Invite a Friend or Team Member?
The invitation process is asynchronous and uses a temporary authentication code to ensure access is granted to the correct account. Coordination must be done between the workspace owner and the collaborator.
Where do I get the code to join a workspace? (Collaborator Action)
If you have been invited to join a workspace, you need to generate your access code and send it to the administrator:
- Access the "My Account" tab on your own dashboard.
- Navigate to the "Authentication" section.
- Click to generate a workspace code (invitation code).
(Note: This code is only valid for a few minutes for security reasons. Share it immediately with the administrator).
How to add the member to the Workspace? (Admin Action)
With the collaborator's temporary code in hand, the workspace owner must:
- In the dashboard, select the respective Workspace and access Settings.
- Go to the Members tab and click Add member.
- Enter the code provided by the user and define the desired permission level (role).
🔐 4. Permission Levels (Roles)
When adding a collaborator, you must assign an access role. We always recommend applying the Principle of Least Privilege: grant only the access strictly necessary for the member to perform their function.
- Viewer (View): Ideal for monitoring. The member can only view dashboards, hardware metrics, real-time logs, and alerts.
- Manager: Focused on service operations. Has all Viewer permissions, plus application lifecycle control (ability to Start, Stop, and Restart services).
- Maintainer: Aimed at the project's developers. Has all Manager permissions, plus source code control (upload/download files, edit code directly in the dashboard, and modify the application's configuration file).
- Administrator (Admin): Full access to the workspace. Has all Maintainer permissions, plus the ability to view and edit sensitive data (environment variables) and execute or restore system Snapshots (backups) do sistema.
⚙️ 5. Management and Best Practices
The workspace owner maintains absolute control over the workspace.
- Immediate revocation: Any member's access can be removed at any time in the settings. Revocation takes effect instantly, terminating the collaborator's access to those applications.
- Role flexibility: You can promote or demote an existing collaborator's permissions without needing to remove and re-add them.
- Update safety: Before allowing a Maintainer-level member to make critical changes to the code structure, ensure a recent Snapshot of the application has been generated to facilitate a rollback if anything goes wrong.
Updated on: 05/20/2026
Thank you!
