In general, Range makes as many operations accessible to any user in the workspace. High-performance teams work best in high-trust environments, and autonomy and agency remove organizational friction.

Even so, some controls are necessary in order to secure sensitive information or prevent inconvenience for other users. In order to do that Range utilizes a combination of role-based access controls (RBAC) and attribute based access controls (ABAC).

Roles

  • Standard The default for all new users.
  • Admin Assignable by the owner and other admins.
  • Owner The person who created the workspace, contact support to reassign.

In App Permissions

Admins and Owners may:

  • Manage user accounts — enable/disable, elevate access level
  • Change the workplace URL
  • Access detailed billing information
  • Access past invoices
  • Manage plan and credit card

Workspace level integrations — e.g. Slack and GitHub — may be restricted to admins on request.

Account Policies

Admins may:

  • Request changes to billing contacts and invoicing
  • Request changes to authentication restrictions (e.g. SSO)

Owners act as the Data Controller for the workspace and may:

  • Approve data deletion requests
  • Approve data export requests
  • Approve account deactivation and deletion

Privacy

By default, check-ins and other information shared in Range may be viewed by any user. Currently, Range does not allow for teams, check-ins, objectives, or entire meetings to be private. Private meeting agenda items are available.

Private meeting items

The Range Meeting tool allows for private notes to be associated with an agenda item. These notes are restricted to attendees, and only attendees may modify a meeting. Attendees added to a meeting in the future are not permitted to see past private notes, however open action items will be visible since they are always carried over to the next meeting.

Did this answer your question?