Managing workspaces and organizations

Managing workspaces and organizations

The organization is the top level: it holds your workspaces, your people, and your licence. Inside it, a workspace groups projects that belong together: a client, a region, a portfolio. Members and Observation Profiles are set per workspace, so a workspace is also the level at which most access is managed.

Both are administrator surfaces. Only organization administrators can open the organization page. Managing workspaces and organizations needs workspace-admin or organization-admin rights.

Opening the organization page

Find it in the left rail, under the manage group.

Section Contains
General Organization name and logo
Licence Your plan, storage, and what is included
Workspaces Every workspace, with its projects and storage
People Organization members and their roles

Checking your storage

The licence section shows how much storage you have and how much is used, and the workspace list breaks it down per workspace.

Check it before a large upload. If a project is bigger than the space left, the upload wizard stops you with Storage limit reached. See Preparing to upload a project.

To free space, delete projects you no longer need. See Moving or deleting a project.

Adding people to the organization

Adding someone here makes them an organization administrator, which is the only role that exists at this level.

For anything narrower, invite at workspace or project level instead. See Inviting people and setting their roles.

Creating a workspace

The workspace list on the organization page is where workspaces are created and deleted. Create one and name it. It starts empty; add projects by uploading into it, or by moving existing ones. See Moving or deleting a project.

Renaming a workspace

Rename from the workspace's settings. The name is only a label. Renaming breaks nothing and affects no links.

Workspace members

Each workspace has its own member list, and a workspace role applies to every project inside it. See Inviting people and setting their roles.

Deleting a workspace

A workspace must be empty first. The delete option stays disabled while it still holds projects, so deleting a workspace is an explicit decision about each project rather than one click that takes everything with it.

To delete a workspace with projects in it, first move the projects you want to keep to another workspace, then delete the ones you do not. Both are in Moving or deleting a project. Once empty, the workspace can be deleted.

Choosing how many workspaces to have

  • Per client or per site works well, because access follows the boundary you already care about.
  • One giant workspace means everyone with a workspace role sees everything.
  • A workspace per project is usually too many: profiles and members must be set up repeatedly.

Since Observation Profiles are workspace-scoped, projects that should share a profile belong in the same workspace.

Troubleshooting

What you see What it means
No organization entry in the rail You are not an organization administrator. Workspace admins manage their own workspaces instead.
Storage figures show a dash The figure could not be read, usually because of a permission.
The licence section says there is no licence If you are certain there is one, contact us; do not act on that message.
No option to create a workspace You need workspace-admin or organization-admin rights.
Delete is greyed The workspace still holds projects. Move or delete them first.
Workspace delete does nothing The workspace still holds projects, or you lack rights for that one.
I can see the workspace list but change nothing You have view access only.
Deleting failed with an error You may lack rights for that particular workspace, even if the option was shown.

Related