Step by step
From the "Requests" tab to the "Send" button
Application
In the "Requests" tab find the application on the list and click "Next".
User
Select the person or several people for whom the request is to be created.
Role
Choose the role in the application. Its description is shown next to the role.
Access scope
Fill in the attributes required for the role, e.g. company, department or resource group.
Summary
Check the details and — if needed — add a comment.
Send
After sending, a confirmation that the request has been created appears in the top-right corner.
Good to know
What affects how the form looks
The form is not the same for every application. Which fields you see in the "Access scope" step follows from the role configuration: some roles have no attributes, others require several. You choose values from lists — you do not type them in, so you cannot enter a company or department that is not in the dictionary.
Start date and expiry date
If the application has the expiry date enabled, you can specify straight away until when the access is needed. When the date passes, sara.next will create a request to revoke the access by itself.
When the form does not let you continue
The most common reason is a limit on people in the role: the administrator may have set that a given role in a given scope can be held by, for example, only one person. Check who currently holds it and, instead of a new request, use "Change user".
Tipsara.next does not suggest which role is right for your position. If you are not sure, ask your line manager or the person responsible for the application.
What happens after sending
The request goes to the approver, then to implementation and — if the process is configured that way — to verification. You follow its progress on the dashboard in the "Pending changes to your access" tile and in the "Requests" tab.
Want to see this on your own data?
During the presentation we will go through the same scenario on applications from your organisation.