Learn About Data Security in Your Model

The foundation of security comes from the user role assignment. For each role, you can define permissions. In the Security Roles area, you can assign general permissions for all models, but you can't assign permissions for individual models. For information on user roles, see Standard Application Roles.

Users must be assigned a role with the same overall model permission level as the model type they want to access. For example, someone assigned only Read access to Analytic Models in their role (and not also granted Update, Delete, or Maintain) will only ever be able to view data from the models they are allowed to read, even if they are additionally granted Update, Delete, or Maintain permissions on those models.

Think of it like a combination: to read a user's private planning model that has been shared with you, you'll need three things:

• Rights to read the model via the sharing rights that are set by the user when they share it.
• Read rights on the Planning Model or Analytics Model application privilege.
• Read rights on the Private Files application privilege.
  Note

  Depending on where the model is saved you might need read rights on either Private File or Public Files application privilege. For example, if the model is saved in the Models folder under Public, you need read on the Public files application privlege. For more information, see Permissions

If you don't have one of these three rights, you won't be able to read (open or use) the model.

Models can be shared the same way that stories and folders can be shared. In the sharing dialog, you can choose the access level for the users or teams that the model is shared with: View, Edit, Full Control, or a Custom access level.

For information about sharing files, see Share Files or Folders.

Adding version security to a model lets you restrict read, write, and delete access to public versions, to prevent other users or teams from changing them. Users who have read-only permission for public versions can still copy data to a private version that they can edit. Users who don't have write permissions can't publish into a public version. With delete permissions for a public version, a user can read, publish to, and delete a public version.

This setting determines whether the model is visible to users other than the owner. If you switch on Model Data Privacy, only the owner of the model and user roles that have specifically been granted access can see the data. Disable this switch if you want the model and data to be public.

For planning models, validation rules let you define the allowed member combinations across multiple dimensions to prevent improper data entry and planning operations in stories and analytic applications. The system validates the data in the model according to the validation rules you define for this model, and planners are only allowed to enter data or use planning functions for the specified member combinations.

Validation rules do not impact data import and data deletion. To prevent planners from deleting public versions, use data access control.

For more information, see Define Valid Member Combinations for Planning Using Validation Rules.

Unlike most other data security features, data locks are designed to change frequently over time. For planning models, data locking lets you prevent changes to specific data at different stages of the planning process, while also delegating control over the lock state to other users.

Except by users with special permissions, locked values can’t be changed by importing or deleting values in the modeler, or by data entry or other planning operations. Data locking doesn’t prevent public version deletion, though; use data access control instead.

For more information, see Configuring Data Locking.