# Workspaces

A workspace in Lora is the home for your team's shortcuts. Every shortcut, folder, tag, and member belongs to a workspace. Workspaces keep teams' knowledge separate. Each one has its own data, members, billing, and permissions.

## Creating a workspace

You can create a workspace when you sign up, or from the workspace switcher in the app. Each workspace has a unique subdomain in the form:

`app.uselora.com/[workspace]`

Pick a name your team will recognize, usually the company or team name.

## Switching between workspaces

If you belong to several workspaces, use the dropdown in the top-left corner of the app to switch between them. Workspaces are fully isolated: your shortcuts, folders, tags, analytics, members, and your role in each are independent.

## Workspace settings

The Owner and Admins can change workspace settings under **Administration → Workspaces**. From here you can:

- Update the workspace name and subdomain
- Upload a workspace logo
- Change the permission toggles (see below)
- Transfer ownership (Owner only)

## Permissions

Under **Administration → Workspaces → Permissions**, two toggles let you tighten what Members can do to shortcuts they don't own. Both default to off, which matches Lora's older "anyone can edit anything" behavior. The Owner and Admins see this section; Members don't.

**Only Admins can delete shortcuts.** Helper text: *Recommended because deleting popular shortcuts can break other users' workflows.*

When this is on, Members can only delete shortcuts they own themselves. Admins and the Owner can still delete any shortcut, with one fixed exception: nobody can delete a Private shortcut they don't own. See the [privacy promise](/docs/members-and-roles#shortcut-ownership).

**Only Admins can edit all shortcuts. Link owners can edit their own.** Helper text: *Generally not recommended. This can increase edit requests, since admins may need to manage changes for shortcuts they don't have full context on.*

When this is on, Members can only edit shortcuts they own. Admins and the Owner can still edit any shortcut, again with the same Private exception.

The toggles only restrict actions on shortcuts owned by *other* people. A Member always retains full edit and delete rights over the shortcuts they personally own. That's a deliberate part of [shortcut ownership](/docs/members-and-roles#shortcut-ownership).

On the **Free** plan the toggles have no effect, because Free treats every member as an effective Admin. Once the workspace upgrades to a paid plan, both toggles start applying as described.

## Transferring ownership

A workspace has exactly one Owner. To hand the role to someone else, the current Owner opens their own member panel under **Administration → Members** and clicks **Leave workspace**. Lora opens a transfer dialog with the oldest Admin pre-filled as the suggested new Owner.

In the dialog the Owner picks:

1. The new Owner. This can be anyone who is currently an active member of the workspace.
2. What role to keep for themselves: stay as Admin, drop to Member, or leave the workspace entirely.

Confirming runs the transfer and the role change in one transaction, so the workspace never ends up without an Owner. The new Owner immediately gains everything the role grants: workspace deletion, and on Enterprise the compliance cluster (billing, audit log, exports, OAuth approvals, security settings).

If the Owner is the only person in the workspace, **Leave workspace** is replaced with **Delete workspace**, because there's no one to hand the role to.

## Deleting a workspace

Only the Owner can delete a workspace. Open **Administration → Workspaces → Delete Workspace**. Deletion is irreversible: every shortcut, folder, tag, member record, analytics row, and audit-log entry tied to the workspace is removed.

Before deleting, export anything you want to keep. At minimum that means the [shortcuts](/docs/import-shortcuts) and the [workspace analytics](/docs/workspace-analytics#exporting-your-data).