Usage roles
Understand Infinite Data's main usage roles and which responsibilities each person normally takes on in the Console.
When to use this
- Use it to decide who should query data, approve access, audit actions, or administer the environment.
- Use it when assembling working groups or reviewing responsibilities.
- Use it when someone received too much or too little access.
Before you start
- Know the person's function in the organization.
- Separate the responsibilities of querying, approving, auditing, and administering.
- Keep a simple rule: each person should receive only what their function requires.
Step by step
- Determine whether the person only needs to query data.
- If they approve or grant access, classify them as an access manager.
- If they investigate evidence, queries, and decisions, classify them as an auditor.
- If they look after users, groups, service accounts, or visible availability, classify them as an administrator.
- Create or choose a group that represents that responsibility.
- Review periodically whether the role still fits the person's current function.
What happens next
- The Console menu reflects the assigned role.
- The person can carry out only the actions expected of their part.
- Role changes are available for auditing.
Common errors
- A person can see an unnecessary area: remove the role or review the group.
- A person cannot complete a task: confirm the right responsibility was assigned.
- Too many accumulated roles: prefer well-defined groups over individual exceptions.
Good practice
- Use groups for recurring responsibilities.
- Avoid broad roles as a way of settling one-off requests.
- Separate who requests, who approves, and who audits wherever possible.
Next steps
Was this page helpful?
Report a problem on this pageDo not send passwords, keys, tokens, or customer data.