Team and User Management

Reoclo uses admin-provisioned team management. Admins add users directly from the dashboard. There’s no self-service signup or email invitation flow. Users can log in immediately after being added.

Roles and Permissions

Every user has a role that determines what they can do within an organization. Roles are assigned per-organization, so a user can be an admin in one organization and a viewer in another.

Role	Permissions
Admin	Full access. Manage users, servers, applications, domains, status pages, and organization settings.
Manager	Manage servers, applications, and deployments. Generate runner tokens. Cannot manage users or settings.
Developer	Deploy applications and manage environment variables. Cannot manage infrastructure or users.
Viewer	Read-only access to everything. Cannot modify anything.

Only admins can add, remove, or change user roles.

Adding Users

Navigate to the Users section in your dashboard and click Add User.

Enter the user’s email address, full name, and select a role. Click Create User.

What happens next:

• If the email address already exists in Reoclo (the user belongs to another organization), they’re added to your organization immediately. They’ll see your organization in their organization picker on next login.
• If the email address is new, a user account is created with a temporary password. The user must change this password on first login.

Users can log in right away. There’s no email confirmation step.

Tip

Share the temporary password securely (via your team’s password manager or encrypted chat). The user will be prompted to set a new password on first login.

Changing User Roles

Go to Users in the dashboard, click the user you want to modify, and select a new role from the dropdown.

The role change takes effect immediately. The user’s next request will use the new permissions. If they’re currently logged in, they may need to refresh the page to see updated UI elements.

Note

You cannot change your own role. Another admin must do it.

Removing Users

Go to Users, click the user you want to remove, and click Remove User.

What happens:

• The user loses access to your organization immediately.
• If the user belongs to other organizations, those memberships are unaffected.
• The user’s global account is not deleted. They can still log in to other organizations where they have active access.
• All user management actions are audit-logged.

Caution

Removal is permanent from your organization’s perspective. To restore a removed user, add them again from the Users section.

Multi-Organization Access

Users can belong to multiple organizations. When a user logs in:

• If they have exactly one organization, they’re redirected to that organization’s dashboard automatically.
• If they have multiple organizations, they see an organization picker where they choose which organization to access.

Switching Organizations

Users with access to multiple organizations can switch between them from the dashboard sidebar. Click the organization name in the top-left corner to open the organization switcher.

Each organization is completely isolated. Data from one organization is never visible in another. When you switch organizations, you’re working in a completely separate environment with its own servers, applications, domains, and user list.

Troubleshooting

User Can’t Log In After Being Added

Cause: The temporary password wasn’t shared correctly, or the user entered it incorrectly.

Fix: Reset the user’s password from the Users section. Share the new temporary password securely.

User Doesn’t See the Organization After Being Added

Cause: The user is logged in with a session from before they were added.

Fix: The user should log out and log back in. The organization picker will show the new organization.

Role Change Didn’t Take Effect

Cause: The user’s browser cached the old permissions.

Fix: The user should refresh the page or log out and log back in.

Can’t Remove a User

Cause: You don’t have the admin role.

Fix: Only admins can remove users. Ask an admin to perform the action.

User Sees “Access Denied” on Resources

Cause: The user’s role doesn’t have permission for the action they’re attempting.

Fix: Check the user’s role in Users. Viewers have read-only access. Developers can deploy but not manage infrastructure. Managers can manage servers and apps but not users. Upgrade their role if they need broader access.

Next Steps

• Access Control and Security: Learn how Reoclo enforces organization isolation and role-based permissions
• Server Management: Add and manage your deployment targets
• Deploy Your First Application: Get your code running on your servers