Create an access template

    An access template is a named bundle of entitlements drawn from several directories and applications at once. Creating an access template describes the access a job role needs as a single unit, so that it can be requested and reviewed as one item rather than entitlement by entitlement. Administrators also create templates to standardize the access a team or a project is expected to hold. Creating a template does not in itself alter anyone's access; access is granted or removed through an access review request or an access certification campaign.

    How an access template is assembled

    SecureAI discovers entitlements from each configured application instance and offers them for selection when a template is built. The Entitlements feature carries the discovery mechanism along with the assignment summary held against each entitlement.

    A saved template holds references to the selected entitlements, kept separate for each instance, together with the field layout and any default values set against a field. Nothing is sent to the source platform at this point. The bundle is read later by the features that act on access.

    Prerequisites

    • Log in as a Super Admin or as a help desk technician assigned a role that includes the Create Templates property of the Access Templates permission under Access Configuration.
    • Configure at least one AI platform instance under Application Settings, with the relevant service associated to it.
    Note:
    • Entitlement values cannot be manually entered. Each one is selected from a list of what SecureAI has discovered.
    • The entitlement types offered vary by application. Two applications covered within the same template might not carry the same set of fields.
    • A category takes effect as soon as it is added, including before the template is saved.
    • Saving a template neither grants nor revokes access.

    Configuration instructions

    1. Navigate to Governance > Access Configuration > Access Templates.
    2. Click Create Access Template.
    3. In the Template Name field, enter a name that identifies the access being bundled.
    4. Against the Select Instances field, click the Add icon (+) and choose the application instances whose entitlements are to be bundled, then click Apply.
    5. Select Category, which reads Default until another is chosen, and choose the category the template belongs in. To create a category, enter a name under Add New and select the plus icon +.
    6. Each selected instance carries its own entitlement fields. Select an instance by name to display its fields and work through the instances in turn.
    7. Next to each field, select the Add icon (+) to view the discovered values. Then, select the check box against each value to be bundled and select OK. The selected values are then shown against the field.
    8. To rearrange or edit the fields, click Enable Drag-and-drop. Fields are dragged into position from the Field Tray. Add Group creates a field group. To rename a field or give it a default value, select the edit control against it and click Edit. Change the field name or the default value under the Enter the Default Value section, then select Done.
    9. Click Disable Drag-and-drop to return to entering values, and then select Save. The template is then listed with its description, category, and the applications it draws on.

    Tips

    • Rename a field based on what a requester will recognize, and set a default value where nearly every request will use the same one.
    • If an entitlement in a template is renamed or removed at the source platform, correct the template rather than the requests already built onto it. Confirm the change under Entitlements first.
    • Give a template its owners before it is used and more than one owner where approvals should not rest on a single person's availability. An access review request can then name the template, instead of listing entitlements one by one.