The following information applies only to Unstructured organizational accounts. To request an organizational account to be created, contact your Unstructured sales representative, email Unstructured Sales at sales@unstructured.io, or complete the online Unstructured contact form.
A workspace is a collection of resources such as connectors, workflows, jobs, and API keys.
Each workspace operates independently of all other workspaces.
A workspace can belong to an organizational account or to a user’s personal account.
Every organizational account begins with one default workspace. An organizational account can have multiple workspaces. (A user’s personal account always has one and only one workspace.)
Users can have access to multiple workspaces within an organizational account.
Each user must be explicitly added to each workspace that they are allowed to access. (A user always has access to their personal workspace within their personal account.) This assumes that the user has first been added to the workspace’s parent organizational account.
To make programmatic API calls to a workspace instead of using the UI, an API key must first exist for that workspace. The caller then uses that API key to make API calls to that workspace. Each API key is valid only for its related workspace.
To create a workspace, you must first have an available Unstructured organizational account.
Currently, only Unstructured representatives can create organizational accounts. To request an organizational account to be created, contact your Unstructured sales representative, email Unstructured Sales at sales@unstructured.io, or complete the online Unstructured contact form.
Your user must have the Super Admin role in the intended workspace’s parent organizational account to create workspaces in that organizational account.
(A user always has one and only one personal workspace within their personal account. You cannot create additional workspaces in personal accounts.)
Sign in to your Unstructured account.
In the top navigation bar, in the organizational account selector, select the name of the organizational account that you want to add a workspace to.
In the sidebar, above your user icon, click the Settings (gear) icon.
Click View All Workspaces.
Click New Workspace.
In the Create New Workspace dialog, enter a name for the new workspace.
Optionally, enter a budget limit for the new workspace. If you do not want to set a budget limit, leave this field blank.
This workspace budget limit is for informational purposes only. Workspace usage is not stopped if this limit is exceeded.
Click Continue.
Sign in to your Unstructured account.
In the top navigation bar, in the organizational account selector, select the name of the organizational account that contains the workspace you want to access.
In the workspace selector, select the name of the workspace that you want to access.
If the workspace selector does not show the workspace you want to access, then your user has not been added to that workspace. To be added to the workspace, contact one of the workspace’s administrators or its parent organizational account’s administrators.
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin role in the workspace to add members to that workspace.
The user to be added must also have the Developer role in the workspace’s parent organizational account.
(A user always has access to their personal workspace within their personal account.)
To add a user to a workspace as a member:
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin role in the workspace to change the roles for that workspace’s members.
A member who is removed from a workspace will no longer have access to the workspace. The member will continue to be able to use their personal account and personal workspace.
Any connectors, workflows, jobs, or other resources that were created by the member within the workspace will not be removed.
The only way to reverse removing a member from a workspace is to add the member back to the workspace.
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin role in the workspace to remove members from that workspace.
(A user cannot be removed from their personal workspace within their personal account.)
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin or Developer role in the workspace to create API keys for that workspace.
To make programmatic API calls to a workspace instead of using the UI, an API key must first exist for that workspace, and then the caller uses that API key to make API calls to that workspace.
An API key can be used only with the workspace for which it was created.
An API key is valid only for the workspace for which it was created.
Deleting an existing API key is a permanent operation. Deleted API keys cannot be recovered.
You cannot use a deleted API key to call the Unstructured APIs.
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin or Developer role in the workspace to delete API keys from that workspace.
Deleting a workspace is a permanent action and is not recoverable. Once a workspace is deleted, all connectors, workflows, jobs, and API keys that are associated with that workspace are also deleted and are not recoverable.
The workspace’s members are not deleted, but they will no longer have access to the deleted workspace’s connectors, workflows, jobs, and API keys.
Any code or scripts that reference the deleted workspace’s connectors, workflows, jobs, or workspace API keys will fail.
A user’s personal workspace cannot be deleted from their personal account.
Only authorized Unstructured representatives can delete workspaces. To request a workspace to be permanently deleted, contact your Unstructured sales representative, email Unstructured Sales at sales@unstructured.io, or complete the online Unstructured contact form.
The following information applies only to Unstructured organizational accounts. To request an organizational account to be created, contact your Unstructured sales representative, email Unstructured Sales at sales@unstructured.io, or complete the online Unstructured contact form.
A workspace is a collection of resources such as connectors, workflows, jobs, and API keys.
Each workspace operates independently of all other workspaces.
A workspace can belong to an organizational account or to a user’s personal account.
Every organizational account begins with one default workspace. An organizational account can have multiple workspaces. (A user’s personal account always has one and only one workspace.)
Users can have access to multiple workspaces within an organizational account.
Each user must be explicitly added to each workspace that they are allowed to access. (A user always has access to their personal workspace within their personal account.) This assumes that the user has first been added to the workspace’s parent organizational account.
To make programmatic API calls to a workspace instead of using the UI, an API key must first exist for that workspace. The caller then uses that API key to make API calls to that workspace. Each API key is valid only for its related workspace.
To create a workspace, you must first have an available Unstructured organizational account.
Currently, only Unstructured representatives can create organizational accounts. To request an organizational account to be created, contact your Unstructured sales representative, email Unstructured Sales at sales@unstructured.io, or complete the online Unstructured contact form.
Your user must have the Super Admin role in the intended workspace’s parent organizational account to create workspaces in that organizational account.
(A user always has one and only one personal workspace within their personal account. You cannot create additional workspaces in personal accounts.)
Sign in to your Unstructured account.
In the top navigation bar, in the organizational account selector, select the name of the organizational account that you want to add a workspace to.
In the sidebar, above your user icon, click the Settings (gear) icon.
Click View All Workspaces.
Click New Workspace.
In the Create New Workspace dialog, enter a name for the new workspace.
Optionally, enter a budget limit for the new workspace. If you do not want to set a budget limit, leave this field blank.
This workspace budget limit is for informational purposes only. Workspace usage is not stopped if this limit is exceeded.
Click Continue.
Sign in to your Unstructured account.
In the top navigation bar, in the organizational account selector, select the name of the organizational account that contains the workspace you want to access.
In the workspace selector, select the name of the workspace that you want to access.
If the workspace selector does not show the workspace you want to access, then your user has not been added to that workspace. To be added to the workspace, contact one of the workspace’s administrators or its parent organizational account’s administrators.
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin role in the workspace to add members to that workspace.
The user to be added must also have the Developer role in the workspace’s parent organizational account.
(A user always has access to their personal workspace within their personal account.)
To add a user to a workspace as a member:
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin role in the workspace to change the roles for that workspace’s members.
A member who is removed from a workspace will no longer have access to the workspace. The member will continue to be able to use their personal account and personal workspace.
Any connectors, workflows, jobs, or other resources that were created by the member within the workspace will not be removed.
The only way to reverse removing a member from a workspace is to add the member back to the workspace.
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin role in the workspace to remove members from that workspace.
(A user cannot be removed from their personal workspace within their personal account.)
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin or Developer role in the workspace to create API keys for that workspace.
To make programmatic API calls to a workspace instead of using the UI, an API key must first exist for that workspace, and then the caller uses that API key to make API calls to that workspace.
An API key can be used only with the workspace for which it was created.
An API key is valid only for the workspace for which it was created.
Deleting an existing API key is a permanent operation. Deleted API keys cannot be recovered.
You cannot use a deleted API key to call the Unstructured APIs.
Your user must have either the Super Admin role in the workspace’s parent organizational account or the Workspace Admin or Developer role in the workspace to delete API keys from that workspace.
Deleting a workspace is a permanent action and is not recoverable. Once a workspace is deleted, all connectors, workflows, jobs, and API keys that are associated with that workspace are also deleted and are not recoverable.
The workspace’s members are not deleted, but they will no longer have access to the deleted workspace’s connectors, workflows, jobs, and API keys.
Any code or scripts that reference the deleted workspace’s connectors, workflows, jobs, or workspace API keys will fail.
A user’s personal workspace cannot be deleted from their personal account.
Only authorized Unstructured representatives can delete workspaces. To request a workspace to be permanently deleted, contact your Unstructured sales representative, email Unstructured Sales at sales@unstructured.io, or complete the online Unstructured contact form.