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

# Workspace

> Live workspace metadata lives at workspace.{table}.

The **workspace** pool is flat and live: `workspace.{table}`. It is a
safe projection of control-plane metadata, not a copy in the lake.
Reads see current membership, connector health, and Plot runs.

V1 tables:

| Table                            | Contents                                            |
| -------------------------------- | --------------------------------------------------- |
| `workspace.users`                | Workspace members (id, email, name, title, status). |
| `workspace.providers`            | Connected tools and sync status.                    |
| `workspace.provider_connections` | Enabled taps on those connections.                  |
| `workspace.roles`                | Roles. Names are display values and can change.     |
| `workspace.role_permissions`     | Permission strings on each role.                    |
| `workspace.user_roles`           | Which users hold which roles.                       |
| `workspace.parables`             | Parables in the workspace.                          |
| `workspace.sql_plots`            | Plots (slug, schedule, enabled).                    |
| `workspace.query_runs`           | Plot run history and spend.                         |

Secrets, tokens, sessions, and credential blobs are not in this pool.

A common join is workspace members against a directory tap:

```sql theme={null}
SELECT
  u.email,
  u.name,
  gu.orgunitpath,
  gu.isadmin
FROM workspace.users AS u
JOIN providers.google.users AS gu
  ON gu.primaryemail = u.email
```

`workspace.users.email` and provider person-email columns are the same
scalar (`Contact.Email`), so that join is valid. Person-email columns
are marked `x-transformPersonEmail` on the tap schema; see
[How taps project into tables](/connectors/tap-projection).
Google Workspace users are at
[`providers.google.users`](/data/providers).

Language-specific Flight SQL clients are on
[Querying the lake](/data#querying-the-lake).