Glossary
This page defines the terms in the Trustle UI and in these docs.
Access event
Section titled “Access event”A record of a change to access or to an eligibility, such as a grant, an extension, a revocation, or a provisioning action. Access events give a history of each access decision. Nobody can edit or delete them.
Access request
Section titled “Access request”A user’s request for access, such as “give me this entitlement for this reason.” A request goes through an approval workflow. After approval, Trustle provisions the access.
Access review
Section titled “Access review”A check of who has access to what. In Trustle, an admin runs an access review as a campaign. Each item goes to a reviewer, usually the person’s manager, who approves or denies it. Trustle records each decision as audit evidence. A deny does not remove access. See Access review campaigns.
Activation
Section titled “Activation”The action that turns a live eligibility into access. The user clicks Activate on My Access, picks a duration, and gives a reason. Trustle approves the activation without an approver.
Admin override
Section titled “Admin override”A policy setting, Allow Admin Override. When it is on, a Trustle admin can approve or deny a request before the designated approvers. It is on unless a policy turns it off.
Approval workflow
Section titled “Approval workflow”The rules that decide who must approve an access request. The Approval Routing options are Manager, Single Approval, Quorum Approval, and Two-Level Approval. You set the workflow on the organization default, a connection, or an entitlement.
Approver
Section titled “Approver”A user whose decision moves an access request forward. The approval workflow of the entitlement decides who is an approver.
Authorization window
Section titled “Authorization window”How long an eligibility stays active. During the window, the user can activate the entitlement without an approver. The Authorization Window setting on the approval policy sets it, up to 730 days.
Basket
Section titled “Basket”A group of up to 20 access requests on one connection that a requester submits together. All items share one duration. Approvers review the basket as one item. A requester makes a basket on the spot. An admin builds a privilege pack in advance.
Break-glass access
Section titled “Break-glass access”Access that an on-call user gets without an approver. The entitlement’s policy must allow it, and the access ends when the on-call shift ends. Request history marks it with a Break-Glass badge, and admins can filter to it.
Connection
Section titled “Connection”A link between Trustle and an external system, such as AWS, GitHub, Okta, or Google Workspace. Trustle finds principals and entitlements through a connection, and uses it for provisioning.
Connection type
Section titled “Connection type”The role of a connection. There are three types:
- Standard: a system that Trustle grants access to, such as AWS or GitHub.
- Identity provider (IdP): the system of record for who your users are, such as Okta, Google Workspace, or Entra ID.
- HRIS: the system of record for employment and reporting-line data, such as Workday.
Deprovisioning
Section titled “Deprovisioning”Removing access in the connected system. Trustle deprovisions when access expires, when an admin removes access, or when a user ends access early.
Eligibility
Section titled “Eligibility”The right to activate an entitlement without an approver, for the authorization window. An eligibility is not access. A user gets one when an approver selects Authorize self-provisioning for this user, when an admin grants a self-provisioning entitlement directly, or when an admin converts standing access.
Entitlement
Section titled “Entitlement”A unit of access that users can request in a connection, such as a group, role, team, or permission set. The Trustle UI says “entitlement” for all of these.
Escalation
Section titled “Escalation”A policy setting, Escalate Unanswered Requests. When nobody acts on a request within the delay, Trustle adds the escalation approvers to the request and notifies them. The delay is from 1 minute to less than 7 days. One escalation approver can approve the request alone.
Expiration
Section titled “Expiration”The date and time after which Trustle removes access or an eligibility. Access with no expiration is standing access. An admin can set, extend, or clear an expiration.
Hidden entitlement
Section titled “Hidden entitlement”An entitlement that an admin marked Hidden. It does not appear on any request surface, for any user, admins included. This includes the request page, Slack, Teams, and Trustle AI. Admins still see it on the connection’s Entitlements tab. Hiding an entitlement removes its pin.
Identity provider (IdP)
Section titled “Identity provider (IdP)”The system that owns user identity for your organization, such as Okta, Google Workspace, or Entra ID. An IdP is a connection of type identity provider. Some connections, such as Google Cloud, delegate identity to your IdP. For those connections, a linked principal on the IdP meets the identity requirement.
Linked application
Section titled “Linked application”A third-party application that a user reaches through the identity provider, through single sign-on or an OAuth consent. Trustle shows linked applications on the Applications tab of a user’s page. An access review campaign can include them.
Linked principal
Section titled “Linked principal”A principal that belongs to a Trustle user. The link lets that user request and receive access on the connection. Compare with orphaned principal and service account.
Maximum Request Duration
Section titled “Maximum Request Duration”The longest time a user can request access to an entitlement. It is a setting on the approval policy. Trustle rejects a request for a longer time. On a self-provisioning entitlement, it is also the length of one activation.
Organization
Section titled “Organization”Your company’s tenant in Trustle. An organization holds your users, connections, policies, eligibilities, access, and audit history.
Orphaned principal
Section titled “Orphaned principal”A principal that no Trustle user owns. It is often an account of a former employee, or an account made outside Trustle. Trustle flags orphaned principals for review.
Pending Acceptance
Section titled “Pending Acceptance”The status of a request that Trustle creates when a user joins a department that has a privilege pack. The user accepts the pack on My Access, in the Privilege Packs section. Trustle then approves the requests and provisions the access.
Permission binding
Section titled “Permission binding”A user’s current access to an entitlement on a connection. It is what the connected system shows the user has now. A permission binding differs from an eligibility, which is the right to get that access.
Pinned entitlement
Section titled “Pinned entitlement”An entitlement that an admin marked Pinned. Pinned entitlements show first in the Request Access list and in the Slack picker. A search ignores pins. See Pinned entitlements.
Principal
Section titled “Principal”An identity inside a connection, such as a user account or a service account. One Trustle user can own many principals, one for each connection. See linked principal, orphaned principal, and service account.
Privilege pack
Section titled “Privilege pack”A set of entitlements that users request in one step, such as Onboarding Pack. An admin builds it. A pack request creates one access request for each entitlement, and each request goes through its own approval workflow. See Privilege packs.
Provider
Section titled “Provider”The vendor behind a connection, such as AWS, GitHub, Okta, PagerDuty, Microsoft, or Google. The provider sets which entitlements and principals the connection can show, and how provisioning works.
Provisioning
Section titled “Provisioning”Granting access in a connected system, for example by adding a principal to a group. An approved access request or an activation starts provisioning. The opposite is deprovisioning.
Requester
Section titled “Requester”The user who submits an access request. Compare with the approver, who decides on it.
Revocation
Section titled “Revocation”Ending access or an eligibility before its expiration. A user, an admin, or a process such as offboarding can revoke access. Trustle records each revocation as an access event.
Self-approval
Section titled “Self-approval”An approver who approves their own access request. By default, Trustle allows it when the requester is also a valid approver for the entitlement. A policy setting can block it, but the UI has no control for that setting. Self-approval is not self-provisioning.
Self-provisioning
Section titled “Self-provisioning”Turning on access without an approver, by activation of a live eligibility. It works only during the authorization window. After the window ends, the next request goes through the full approval workflow. See Self-provisioning.
Service account
Section titled “Service account”A principal that is not a person, such as a bot, an automation, or a system integration. Bulk actions for people, such as expiring all standing access, skip service accounts.
Session
Section titled “Session”One period of active access from an approved request or an activation. It ends at its expiry. A user can end a self-provisioned session early with End Now on My Access.
Standing access
Section titled “Standing access”Access with no expiration. It stays until someone removes it. Compare with just-in-time access, which expires on its own.
Trustle AI
Section titled “Trustle AI”The chat assistant in the Trustle web app. It answers questions about access and about Trustle, and helps find an entitlement to request. It is for admins, if your organization has it enabled.