Requesting access
People who cannot see or do something they need can ask for it from inside Delegaris. An administrator grants it by making an access rule, usually with an end date. This page covers both sides.
Asking for access
You can ask from two places:
- the Resources page, with Request access at the top right
- My account, with Request access in the What you can do section, where you can also see the access you already have
The Request access dialog asks:
| Field | What to enter |
|---|---|
| What you need to do | Tick any of Start, Stop, Reboot, Keep on past the schedule, Connect with Remote Desktop |
| Which machines | Names, IDs or a tag, as you know them. For example: uat-web-1, uat-web-2, or everything tagged Project = Atlas |
| For how long | A day, A week, A month, Three months or For good |
| Why | What you need it for, for example "Testing the Atlas release this week" |
Press Send request. The administrators are told, in Slack if it is set up, and you hear back on the page and in Slack.
- You can have up to 5 requests waiting at once.
- Administrators do not see Request access, because they can already do everything.
- To ask for tag rights, ask an administrator directly; the dialog covers the actions above.
Following up
Your requests are listed under Your requests for access on My account:
| Status | Meaning |
|---|---|
| Waiting | Not decided yet. Withdraw takes it back |
| Granted | A rule was made. It works now; check What you can do |
| Declined | Not granted, with the administrator's note if they left one |
| Withdrawn | You took it back |
Answering requests
Administrators see waiting requests on the Approvals page, under Requests for access, and they count towards the number beside Approvals in the top bar. Each shows who is asking, for what, for how long, when they asked and their reason.
Granting
- Press Grant…. The access rule editor opens, already filled in:
- Who: One user, the person who asked
- Can: the actions they asked for
- Tags the resource must have: any
Key = Valuethey wrote under Which machines - Specific instances or databases: the rest of what they wrote, split at spaces, commas and semicolons, without words such as "everything" or "tagged". Next to a tag, only parts that look like a machine name or ID (with a digit, hyphen, dot or underscore) are kept
- Ends: the time asked for from now, or empty for For good
- Rule name: their name and what they asked for
- Check what the rule covers. People write names as they know them, so the names often need correcting to IDs, or replacing with a tag condition. Press Show what this covers to see what it matches.
- Adjust anything else, for example add an Accounts limit, or tick Only with approval.
- Press Grant.
The rule is made, the request is marked granted, and the person is told in Slack, with the end time if there is one. The new rule appears under Settings > Access like any other and can be edited or deleted later.
A request for "uat-web-1 and everything tagged Project = Atlas" arrives with the tag condition Project = Atlas and the name uat-web-1. A rule needs a resource to match every part filled in, so a tag and names together cover only those names that also carry the tag: for "these machines, or anything tagged…", grant two rules. Check with Show what this covers before granting.
Declining
Optionally type a note in Note (optional), then press Decline. The person is told, with the note.
Activity
The activity log records each request, withdrawal, decline and grant, and the rule a grant made, each under the name of the person who did it.
Next steps
- Access rules
- My account
- Approvals, for actions that need agreement each time