> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand workspace-scoped resources

> Learn how Biqli keeps links and related resources within a workspace.

Resources created in Biqli belong to the workspace selected at creation time. A link in one workspace is not automatically visible in another, even when the same person belongs to both.

Custom domains can be attached to another eligible workspace on the same account after ownership checks. Other supporting resources, such as folders, tags, pixels, and API keys, keep their own workspace scope.

API keys are workspace scoped by design. They do not need a separate Workspaces permission and cannot be used to browse another workspace.

## Resource relationships

A link can reference folders, tags, tracking pixels, a custom domain, and an
attached QR code. Those related resources must be accessible in the same
workspace context. An API operation also needs read permission for referenced
resources in addition to write permission for the primary resource.

## Switching does not move data

Selecting another workspace only changes the active dashboard context. It does
not copy or transfer resources. Use an explicit transfer workflow for a link
when available, then review domain and attachment differences in the destination
workspace.

## Shared verified domains

A verified custom domain can be attached to another eligible workspace owned
through the same Biqli account. This reuses DNS verification, but it does not
merge the workspaces or share their links, members, analytics, or API keys.

Always use stable resource IDs when integrating across dashboards because names
can be repeated in separate workspaces.