Organisations are shared accounts that groups of people use to collaborate across project(s).
Pro Tip: Consider assigning a meaningful name to your Organisation, such as, e.g., the name of your project.
We’ve seen before that an Organisation is associated with as many users as you want. However, there’s only one email associated with owning this Entity. Nonetheless, you or any appointed Admin may change it, for any reason needed.
For now, if you want to delete or update an Organisation’s details, you need to contact Statful’s support.
When we talk about an Organisation as a Group, we are referring to Organisation Entities and not the User who created them. This reference is meant solely to indicate that the Ownership of those Entities is transversal to everyone on the same Organisation, i.e., anyone can edit them.
We can use the Identity and Access Management (IAM) expression to identify Users and Roles as IAM Entities since they are used together to assign access and privileges on Statful. As such, the following titles should make clear on what is particular to each Entity.
Since the User is the one who creates and manages all Entities, within its level of access, we can say that users are the main actors of Statful.
Every person who uses Statful has their own User account, that is influenced by:
- a Role (e.g., Admin),
- Ownership of Entities (User’s, or Organisation’s).
Both themes are defined by default Permissions, e.g., the Ownership of User Entities determines a User’s permission to manage them.
Let’s look into better understand this idea next.
A User’s Role in your Organisation defines their level of access to your Organisation, its settings, and your data. They determine what the User (specifically) can and cannot do.
Currently, Statful defines two built-in roles:
- User (read) - can create any User Entity (Dashboard, Groups and Widgets), and has basic Permissions to Organisation Entities (Metrics, Timelines, Alerts and Notification Profiles);
- Admin (read and write) - inherits the above, and has advanced Permissions to the rest - IAM (Users and Roles) and Organisation Entities;
Note 1: To learn how and where to go to manage your Users, delegate Roles or delete them, please refer to this section.
Note 2: Custom roles are planned for a future release.
Besides the typical read and write permissions (see reference below), the User may also benefit from the Ownership privilege, where when creating a User Entity, the Owner can also manage (read and write) it.
Each permission encloses the following:
the User can visualise the Entity, but they cannot make changes to it.
the User can visualise and make changes to the Entity, including deleting it.
We’ve also mentioned that Ownership over Entities (User) allows full control over the created Entity. This facilitates cooperation among Users, where an Owner of a Dashboard, e.g., can either share it with another User or Transfer Ownership of that Entity.
Note: Only an Owner can share their Entity with others.
Let’s review our Ground Rules:
- An Owner is any User that creates or holds Ownership over a User Entity (Dashboard Groups, Dashboards and Widgets);
- Owners have Write permission over their Entity;
- Only Owners can share or transfer Ownership of their Entities with others;
- Admins have full administrative control (Create, Edit or Delete) over any Entity;
- Admins can assign Permissions to other Users;