AutoHub roles are TaskSultan roles. They are separate from UiPath tenant roles and from permissions in Orchestrator.
#Workspace administration
| Role | Responsibility |
|---|---|
| Organization Administrator | Creates the workspace, controls membership, security settings and integrations. |
| AutoHub Administrator | Configures AutoHub categories, lifecycle rules, templates and reporting. |
| Contributor | Submits ideas and adds evidence or comments. |
| SME / Process Owner | Explains the work, validates requirements and approves the specification. |
| Reviewer / Approver | Decides whether an idea or specification may move to build. |
| Automation Developer | Captures targets, uses Builder, validates the draft and prepares delivery. |
| Viewer | Reads permitted records and evidence without changing workflow state. |
The first person who creates a workspace becomes its initial Organization Administrator, unless the deployment or invitation flow assigns that responsibility explicitly. An AutoHub user does not automatically become a UiPath user or an Orchestrator user.
#Access boundaries
Roles should be assigned to the least privilege needed for the person’s work. Integration permissions remain controlled by UiPath separately.