Introduction to Access Rights

This article is an introduction to access rights in Pigment and is required reading before you start to establish your security plan. It explains the essential basic concepts before you start setting up access rights in Pigment.

What are Access Rights?

Access rights are a form of data security that allows you to configure what data individual users can see and interact with.

So, how are access rights different to Permissions?

• Permissions define the specific actions a user can do in Pigment, such as creating new Metrics, Boards, and Lists.
  For example, Permissions determine if a Member can create a new Board or write different formulas. However, access rights determine if a user can read or write data for a specific country or department on a Board.
• Access rights are strictly related to data and how users can interact with that data.

Where are Access Rights Created in Pigment?

You set up access rights by creating rules in a Metric that is set to the data type access rights. It defines how users can interact with data. You use this with a User List Dimension, and with any other Dimension list on which you want to apply data security.

For example, if you wanted to give users access to different Country data, you create your Metric using a User List and Country Dimension List. When the Metric is created, you then assign that Metric to data using rules.

The number of access rights Metrics you need depends on your security needs. However, it’s certain that you’ll use multiple Metrics and multiple functions, including the ACCESSRIGHTS function, for a more scalable set-up.

Access Rights Options

• Types of Data Access
• Define the Scope of Access Rights Rules
• Define Where Access Rules Apply
• Using Multiple Access Rights Rules on a Dimension

Types of Data Access

When you create an access rights Metric, you need to assign the read and write settings for users. You’ll see there are two separate options for both settings:

• Read/Write. These options allow users to read or write data.
• No Read/ No Write. These options prevent users from reading or writing data.

If you need to:

• Hide data from a user, set this to No Read / No Write.
• Give a user read-only access, set this to Read/ No Write
• Give a user write-only access, set this to Read and Write.

Define the Scope of Access Rights Rules

The access rights configuration within the User Roles is applied to the entire Application by default.  However, when you create new rules, you need to define the scope of the rule.

There are two options, Apply or Ignore: 

• Apply is used to define which parts of the application this rule is enforced.
• Ignore is used to limit the scope of an existing rule.

For example, you could set up an access right rule to Apply to every Metric that contains the Employee Dimension. However, there may be specific Metrics where you don’t want to apply this rule. In this situation, you create a second rule, set it to Ignore, and apply this new Ignore rule to the excluded Metrics.

Define Where Access Rules Apply

After you decide if a rule is used to apply or to remove access rights, you have to define where in your model that it applies. This option protects data primarily in Metrics, but also in Lists.

You can select:

• Specific Metrics. 

  Select one or more Metrics that contain the Dimensions used in your access rights Metric.

  If you created an access rights Metric that used the User list and the Country list, you could select Specific Metric(s) that contained the Country list.

• All Metrics using specific Dimensions.

  Assign this rule to all present and future Metrics that contain Dimensions used in your access rights Metric.

  For example, if your access rights Metric contained a Dimension called Department, then this rules is applied to all Metrics containing the Department Dimension.

• Specific List Properties. Define on which Lists and on which Properties of this List these access rights should apply to.
  For example, specific access rights for the Annual Salary property of my Employee list.

• List Item Values. This rule filters out values in the List according to the Metric of access rights. It allows you to protect data in Lists, based on Properties.
  For example, you can set Read access on Annual Salary property based on a Dimension formatted Country Property. This allows certain Members to view some Salaries depending on the Country Property.

Using Multiple Access Rights Rules on a Dimension

The most restrictive permission in Pigment is No Read / No Write. When you have multiple access rights rules applied to a Dimension, this permission applies.

Default access rights are determined by Role. If the Role default Access Rights is set to No Read / No Write, it overrides other access rights settings due to it being the most restrictive setting.

For example, a Member with the Reader role set to No Write cannot edit data, even if another rule allows writing. The most restrictive setting always takes precedence when multiple rules apply to the same part of an Application.

When access rights are defined in multiple Metrics, the most restrictive rule prevails. The exception to this is if you create a rule using the Ignore option, indicating that the Users roles configuration doesn’t apply to a specific set of data.

As a default setting, we recommend that you set access rights in roles to No Read and/or No Write based on the sensitivity of your data. This ensures Members have no immediate access to the data when they’re invited into the Application.
 

Assign Access Rights to Roles

The assignment of access rights begins at the highest level with roles.

You need to define permissions and access rights when you set up a new role in Pigment. The access rights that you define for a role are considered to be default setting when no other rules are applied.

For example, let’s say a Member’s access rights is set to Read/ Write. This user can edit or write any data if there are no other rules applied.

This is why you need to apply a more granular security setting to indicate precisely which data users can see, read or edit. You can also establish where in Pigment an access rights rule doesn’t apply, or where it should be ignored.

Preview a Member’s Access Rights

When you set up Access Rights for a Member, there are three possible states:

• No Access. The Member cannot see the data.

• Partial Access. The Member can read some of the data but not all of it. Depending on their configuration, they may be able to edit data.

• Full Access. The Member can read all of the data. Depending on their configuration, they may be able to edit that data as well.

Depending on your security needs, you can assign access rights to individual Members and adjust them to different levels of granularity within an Application. This flexibility allows you to specify exactly which data each user can read, write, or hide.