- Getting started
- Best practices
- Tenant
- Actions
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Action Catalogs
- Profile
- System Administrator
- Identity Server
- Authentication
- Other Configurations
- Integrations
- Classic Robots
- Troubleshooting
Personal Workspaces
A personal workspace is a modern folder available for the dedicated use of a particular attended user. You can enable Personal Workspaces for the users and user groups to which you wish to grant robot access using attended modern robots. If enabled, this workspace is automatically created when the user is provisioned in Orchestrator.
Personal workspaces come with their own dedicated package feed by default, meaning packages are kept separate and only available in the specific workspace they have been published to. Any package that is added to the workspace gets automatically deployed as a process in the workspace.
Packages stored in a user's personal workspace exist outside of the main Orchestrator feed and thus are not visible or accessible by other users. For each package uploaded, a corresponding process is automatically created (or updated in the case of existing packages and processes), enabling the user to launch their automation almost instantly after publication, no Orchestrator access or actions needed.
Orchestrator automatically manages machine templates for personal workspace owners. A machine template with a Studio runtime is automatically created and assigned to each new personal workspace. This removes unnecessary overhead from the developer who can begin working in the context of that workspace right away. That includes publishing automation projects and launching jobs from Orchestrator for debugging purposes.
Users that work in other folders besides their personal workspace can benefit from the Orchestrator debugging capabilities of their machine template by assigning it to the folders they are working in (i.e., the folders they have been assigned to).
- Packages / Processes
- Jobs
- Assets
- Logs
- Queues and Queue Items
- Storage Buckets (if the functionality is enabled at the tenant level)
Users with administrator privileges can handle all personal workspaces in a tenant from the Personal Workspaces page. On this page, you can check the last login time of the workspace's owner and can perform several operations:
- See usage - shows an overview of the entities and running/pending jobs in the workspace.
- Convert them into folders - converts the workspace into a modern folder with its own package feed while creating a blank workspace as a replacement for the initial one.
- Exploring their contents - allows accessing the contents of the personal workspace. The original owner of the personal workspace is properly notified whenever a user begins or ends an exploratory session.
- Deleting them
- Active - The owner is an active Orchestrator user.
- Inactive - The owner is not an active Orchestrator user i.e. has been deactivated.
- Orphaned - The owner no longer exists as a user in Orchestrator.
Tenant Context > Folders > Personal Workspaces tab
See Managing Personal Workspaces for details.
You can enable personal workspace creation for a user/user group when creating or editing the user entity on the Users page.
Tenant > Users
You can mass enable personal workspaces for all users that use a certain attended licensing profile irrespective of their group membership.
Tenant > Settings > General > Personal Workspaces
Depending on the Orchestrator UI needs, you can choose between two UI profiles for users with personal workspaces.
-
Standard Interface - Users see the default Orchestrator menus and can select their personal workspace from the folder picker
-
Personal Workspace - Users see a modified UI with no side-menu and only the entities listed above.
Note: You cannot change the UI profile for yourself as a means to prevent accidental disabling of core functionality.
