- Release notes Cloud Action Center
- Getting started
- Activities
- Designing long-running workflows
- Start Job And Get Reference
- Wait For Job And Resume
- Add Queue Item And Get Reference
- Wait For Queue Item And Resume
- Wait For Form Task And Resume
- Resume After Delay
- Assign Tasks
- Create External Task
- Wait For External Task And Resume
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Get App Tasks
- Add Task Comment
- Update Task Labels
- Create App Task
- Wait For App Task And Resume
- Configure task timer
- Actions
- Processes
- Notifications
- Audit

Action Center
Flex licensing
If you enrolled in Unified Pricing Plan instead, refer to Unified Pricing licensing.
Action Center licenses cover two primary actions:
- Create Action Center tasks in Studio.
- Access and manage actions in Action Center.
The following table lists the licenses that grant access to either Action Center or the ability to create tasks in Studio.
Licenses | Action Center access | Task creation access |
---|---|---|
Action Center - Named User | ||
Attended - Named User | ||
Citizen Developer - Named User | ||
RPA Developer - Named User | ||
Automation Developer - Named User | ||
Cloud - Basic - Named User*
* This license type applies only in the context of Automation CloudTM. Therefore, Cloud - Basic - Named User works only when both Action Center and Orchestrator are deployed in cloud. |
If you or another user logs into Action Center without a valid license, the following banner will be displayed in the page header: You have more licenses allocated to your services than you have available to your organization. Please adjust the license allocation.
Edit your license allocation to guarantee that all users have a valid license to access Action Center. Read more information about how to assign licenses in the Assigning user licenses page.
The Action Center license count depends on the license allocated to each user. When an account is created in UiPath, a license this does not automatically consume a license. Existing users, with corresponding accounts are assigned specific user licenses based on their roles or requirements. Every user with a Named User License, that offers access to Action Center, is counted as one consumed license.