Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Overview

Profiles and Profile Grants are designed to improve efficiency across the organization. They are the evolution of Business Roles, allowing for more streamlined user onboarding and cutting back the number of permissions to be reviewed in access reviews. Profile grants come in two levels: birthright and suggested, giving administrators more control over which permissions are provisioned during onboarding. Both birthright and suggested profile grants can be pre-approved in an access review.

Terminology

Profile: A collection of user demographic properties based on roles in your organization, such as Department = Engineering & Title = Engineer. A user may be associated with zero or more profiles, and there may also be a profile for All Users.

Profile grant: A mapping between a profile and a permission.

Birthright level: Indicates that all users in the profile should have the permission.

Suggested level: Indicates that all users in the profile may have the permission.

Profile grant states:

  • New: Grants suggested by Zilla but not yet activated.

  • Activated: Grants that are used for onboarding and access reviews.

  • Deactivated: Grants that are no longer used.

Profile actions:

  • Activate Grant - Makes profile grants eligible for onboarding and access reviews.

  • Deactivate Grant - Declined grants will not be used for onboarding nor access reviews.

  • Reassign Approver - By default, the Technical Owner of the permission’s application is the approver of the profile grant. Reassignment can be to TBD.

  • Edit Level - Zilla’s suggestion of either birthright or suggested can be manually overridden.

Generating Profiles

The Zilla administrator initiates profile generation. The tenant’s data is analyzed to create a collection of profiles each with a collection of profile grants. Profile grants originate in the New state and must be activated before they can be used in an access review or for provisioning. By default, an application or permission owner is responsible for reviewing and activating profile grants, but Zilla admins can also activate.

See How to Generate Profiles for a step-by-step guide.

Reviewing New Profiles

When Profile generation completes, the profiles will be presented in a table on the Profiles page along with summary information. See below for details.

Annotated-Profile-Image.jpg

(1) Profiles grants can be viewed in several different ways: By Profile, By Application, List.

(2) Active User Permissions: Displays the count of permissions across all accessible applications that are mapped to active users.

(3) Total Grants: Displays the total number of grants by state. See state definitions in Terminology.

(4) Total Profiles: Shows the average number of profile grants per profile and the number of applications with profiles.

(6) Search and Filter provides the ability to search the profiles and filter by Profile and Last Updated.

(5) The Profile table includes the following columns:

  • Profile: User attributes shared by a population of users.

  • Users: Number of users matching the profile.

  • New/Notified/Active Grants: Number of profile grants within the profile by state.

  • Last Updated: Displays when this profile grant’s status was last updated.

  • Actions: Click View to see a list of grants for the profile to take an action. See actions definitions in Terminology.

Activating New Profile Grants

Before a profile grant can be used by the Zilla application in either onboarding or user access reviews, it needs to be activated. Activation is the responsibility of the Application’s Technical Owner (by default) but any admin can also activate a profile grant.

See How to Activate Profile Grants for a step-by-step guide.

Customizing Profile Generation

After the initial profile generation, the administrator can re-generate profiles at any time and specify the scope in terms of the population and which demographic values to use. The user demographic fields available to choose from are based on the tenant's collected user metadata. In order to be included, the field must be collected and populated. The administrator can also change the system defaults regarding minimum quality and population of profiles.

See How to Customize Profile Generation for a step-by-step guide:

  • No labels