Request onboarding¶
When a new person joins your organization, an onboarding request ensures they get the right access to the applications they need. Permission Assist walks you through the process and uses your organization's access models to automatically determine what access the new person should have.
Note
Before you begin, you must initiate a personnel event, select Onboarding, and then select Start.
Step 1 — Enter the employee's information¶
-
Enter the required personnel details for the person being onboarded. At a minimum, you must provide the employee's first name, last name, and identity type. See the personnel details fields below for a description of each field.
Tip
The more information you provide (such as department, title, and office), the more accurately Permission Assist can match the employee to the right access models.
-
Select the Continue button. The access models are displayed.
Step 2 — Review the access models¶
The employee's information is summarized at the top of the page, and the access model matching section is displayed below.
-
Review the Automatic section. If the employee's information matches one or more access models, the matched access models are displayed here. These are included automatically and determine the applications and permissions the new person will receive.
-
(Optional) Review the Optional section. If additional access models are available, you can select any that apply to this person.
-
Select the Continue button. The "When is access needed by?" section is displayed.
Step 3 — Choose when to start¶
-
Select one of the following options:
Option Description Immediate Select this option to start the onboarding process as soon as possible Scheduled Select this option to schedule the onboarding for a future date and time. After selecting this option, select the date and time link next to Needed by, then select the date and time the work needs to be completed. Use the slider to select the time (see example below)

Note
If you schedule the onboarding, Provision Engineers may be able to start working early based on the working window configured in System Configuration > Taskboards > Personnel Events.
-
Select the Continue button. The "Any additional instructions or explanation?" section is displayed.
Step 4 — Add comments and submit¶
-
(Optional) In the comment area, enter any additional notes or instructions that may be helpful for the Provision Team as they set up this person's access. You can also add attachments to comments and use @mentions to send email notifications to other Personnel Managers, Security Team, or Provision Team members.
-
Select the Continue button.
- Verify the information.
- Select the Submit button. The onboarding request is created.
Personnel details fields¶
| Field | Description |
|---|---|
| Image | Associates an image with the new identity. If an image is not uploaded, a default image is assigned |
| First Name (required) | The employee's first name |
| Last Name (required) | The employee's last name |
| Type (required) | The identity type. Identities can be classified as specific types such as employee, service account, vendor account, and so on. Identity types can be helpful for sorting and searching, and can also be used by Permission Assist to create recommendations or filter reviews |
| Description (optional) | A description or additional information about the employee |
| Company (optional) | The company this employee belongs to. Depending on how your access models are defined, this may determine which access models the identity is enrolled in. You can add a new company by typing the name. To clear this field, hover over the field and select the Delete button |
| Division (optional) | The division this employee belongs to. Depending on how your access models are defined, this may determine which access models the identity is enrolled in. You can add a new division by typing the name. To clear this field, hover over the field and select the Delete button |
| Department (optional) | The department this employee belongs to. Depending on how your access models are defined, this may determine which access models the identity is enrolled in. You can add a new department by typing the name. To clear this field, hover over the field and select the Delete button |
| Office (optional) | The office or branch this employee belongs to. Depending on how your access models are defined, this may determine which access models the identity is enrolled in. You can add a new office by typing the name. To clear this field, hover over the field and select the Delete button |
| Supervisor (optional) | The employee's supervisor. If the Security Team creates a review that includes reviewing supervisors, this field determines which review items are assigned to each supervisor. You can add a new supervisor by typing the name. To clear this field, hover over the field and select the Delete button |
| Title (optional) | The employee's job title. Depending on how your access models are defined, this may determine which access models the identity is enrolled in. You can add a new title by typing the name. To clear this field, hover over the field and select the Delete button |
| Additional fields (optional) | If your organization has enabled additional fields in System Configuration > Identities, those fields appear here. You can enter a value for any that apply to this employee. |
What happens next¶
After the onboarding request is created, it moves through the personnel event workflow. An authorized person must approve the request. After the event is approved, it moves to the provision stage where Permission Assist automatically creates access requests for the Provision Team to set up the employee's access. For more information, see How personnel events work.
Related topics:
- Initiate a personnel event
- Change the scheduled start date of a personnel event
- Add attachments to comments
- Use @mentions to send email notifications