Understanding Reemo Roles & Licenses
What are the different roles in Reemo ?
| Role | Scope of Access | Access to Settings | Organization Visibility | License Usage |
|---|---|---|---|---|
| User | Only assigned computers | ❌ No settings access | ❌ No organization or group visibility | ✅ If enabled and has computer access |
| Group Admin | One group or subgroup | ✅ Group and subgroup-level management | ❌ Only their group(s) | ✅ Takes 1 license |
| Organization Admin | One organization | ✅ Org-level settings | ❌ Only their organization | ✅ Takes 1 license |
| Instance Admin | Entire Reemo instance | ✅ Full instance settings (branding, security, all orgs) | ✅ All organizations | ❌ No license required |
Administration & Management
Does an administrator need a Reemo license?
No, an administrator does not need a license to simply manage the organization. However, if this administrator also wishes to use Reemo to connect to remote machines, they will need a license just like any other user. (See: Licensing)
One of my users gets an "Error 560" and cannot connect.
Error 560 is most often caused by a required security setting not being met. The most common case is that two-factor authentication (2FA) has been made mandatory for the organization, but the user has not yet set it up on their account. (See: Security Settings)
How can I make sure users only connect during working hours?
You can configure access schedules to define specific time windows during which users are allowed to access machines. If a user cannot connect, check that their access schedule is correctly configured. (See: Usage Schedules)
How can I disable copy-paste and enforce automatic logout after inactivity?
Both options are available in your organization’s security settings. There, you can disable clipboard sharing and configure a session timeout (auto-logout). (See: Security Settings)
How can I convert an “External User” into a “Managed User”?
It’s not possible to directly convert an account. The process is to first remove the external user (the user must do it themselves or request assistance from Reemo support), then you can re-invite them as a managed user.
One of my users (SSO) cannot log in.
When configuring SSO (SAML), always test it with a user who does not have the “Owner” role. The “Owner” account should not be bound to SSO to avoid being locked out of the organization during setup.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article