Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Term

Definition

GroupAccessPrivilege

A group access privilege entity is a POSIX Extended Access Control List (ACL) narrowed to group-level ownership.

A GroupAccessPrivilege consists of:

[ Collection, Owner, Group, Permissions ]

Collection

The collection of Entities to which this GroupAccessPrivilege applies.

Owner

The group that controls this GroupAccessPrivilege.

Group

The group to which access is granted.

Admin-user

End-user with admin privileges with access to all resources within ModelOp Center.

Additional privileges:

  • Able to manage Model life Life Cycles.

  • Able to manage RWX Permissions.

Non-admin user

End-user without admin privileges, that can access only resources associated to the groups that given end-user belongs to and resources available through a given Read, Write or Execute GroupAccessPrivilege.

No additional privileges:

  • Can’t manage Model Life Cycles.

  • Can’t manage RWX Permissions.

Permissions

The set of granted permission.

Available permissions:

[READ, WRITE, EXECUTE]

READ Permission

A user who has READ permissions will have view only access to the given entity. For example, READ access to a Business Model permits the user to see the Use Case or Model, and all of its relevant information , such as assets, documentation, jobs, test results, and associations. A user with READ permissions only cannot modify the given entity.

WRITE Permission

A user who has WRITE permissions will have the ability to modify the given entity. For example, WRITE access to a Business Model permits the user to edit the information/metadata about the Business Model and add/edit assets, associations, and documentation. For a Model snapshot, a user with WRITE permissions may also add monitors.

EXECUTE Permission

A user who has EXECUTE permissions will have the ability to run specific tasks for the given entity. For example, EXECUTE access to a Business Model permits the user to create a Snapshot (“version”) of the model. For a Snapshot, EXECUTE access allows the user to run tests/monitors, create jobs, and deploy models.

...