Workspace settings

Workspace settings live at /{handle}/settings (which opens on the General tab). There are exactly eight tabs, in this order: General, Members, Permissions, Jira, Webhooks, Access tokens, Connectors, Audit log. Two of them — Permissions and Audit log — are Owner-only, carry a small "Owner" caption, and are hidden from everyone else.

General

Described as "Your workspace's identity and address.", the General tab holds:

• Workspace card — the workspace Icon ("Square PNG or SVG"), the Name (editable by Owner and Admins, up to 120 characters) and the Workspace URL ("Where your team finds it"), showing laya.net/{handle}.
• Plan card — carries an "Early access" pill and reads "Free, unlimited usage": Laya is free while it is in early access, with no cap on members, boards or storage and no payment details held. AI features have a daily fair-use limit — if you hit it, Laya shows "The AI usage limit for this account has been reached. Try again later." and the limit clears when the daily window resets. A tooltip notes licensing options come later, with notice before anything takes effect.
• Custom subdomain card — marked "Planned". A future release will let a workspace live at its own subdomain; it is not built yet.
• Danger zone (Owner only) — Delete workspace. You must type @{handle} to confirm, and the warning is blunt: "This permanently removes the workspace, its boards and members. This can't be undone."

Members and Permissions

The Members tab ("People in this workspace. Roles control what each person can see and do.") is covered in Managing members, and the Owner-only Permissions matrix in Roles and permissions.

Jira

The Jira tab ("Jira sites mirrored into this workspace and their sync health.") lists each Jira connection with a Shared/Private pill, a health word (Healthy, Degraded, Broken or Disabled), the number of mapped boards, when it last synced ("Synced …" or "Never synced"), who installed it, and the last error if any. The connection's own Manage page describes the same underlying states in different words: Broken appears there as "Needs attention" and Disabled as "Idle" — see Sync health, logs and recovery.

Webhooks

The Webhooks tab ("Send workspace events to your own HTTPS endpoints.") lets you register an endpoint URL, subscribe to any of eight event kinds — ISSUE_CREATED, ISSUE_FIELDS_PATCHED, ISSUE_STATUS_CHANGED, NOTE_POSTED, SPRINT_CREATED, SPRINT_UPDATED, EPIC_CREATED, EPIC_UPDATED — and pick a Format: "Native (Laya JSON)" or "Slack (Block Kit)". The signing secret is shown once, at creation. Each webhook row offers Probe, Log and Delete.

Access tokens

The Access tokens tab ("Personal API tokens for scripts and integrations. Treat them like passwords.") is an Owner capability. It shows a copyable Workspace ID, then a form with a Label and a multi-select of Scopes: org:read, boards:read, boards:write, issues:read, issues:write, docs:read, docs:write, webhooks:manage, crm:ingest. The token value is revealed once; existing tokens show their prefix, scopes and last-used time, with a Revoke action.

Connectors

The Connectors tab ("GitHub, Slack and AI connections for this workspace.") lists GitHub and Slack connectors with a status dot and last-sync time. Each row has Test — which reports "Probe succeeded in N ms." — and Reconnect. For connecting new tools and the full picture across providers, see Managing connections.

Audit log

The Audit log tab (Owner only) records "role changes, removals, ownership transfers, renames, invitations, and Jira disconnects". Entries are human-readable — for example "changed a member's role", "invited someone", "joined the workspace", "transferred ownership", "updated workspace settings", "disconnected a Jira site" and "updated role permissions".