Privacy and analytics

We use necessary technical cookies and, only with your consent, analytics and marketing pixels to improve the website and measure campaigns.

Privacy policyCookie policy
Docs
English
EspañolEnglishFrançaisDeutschItalianoPortuguês

Getting started

  • What is Nömad?
  • Getting started with Nömad
  • Create your brand and complete the Genome
  • Invite your team
  • Glossary

Brand OS

  • What is inside Brand OS
  • What is the Genome?
  • Who is Nödo?
  • What does a Brand Manager do?
  • Brand Kit and Library
  • Posts and calendar
  • Connections
  • Meetings

Work

  • Work and tasks
  • Ordering work
  • Following, reviewing and approving deliveries
  • Custom quotes
  • Yes, there are humans behind it

Account and billing

  • Plans and pricing
  • Billing and payments
  • Roles and permissions
  • Workspaces and multiple brands
  • Languages, apps and data
  • Leave, close or delete: account, brands and workspaces

Help

  • How to get help

API

  • Brand API
    • Permissions and roles
    • Brand
    • Genome
    • Brand Kit
    • Library
    • Works
    • Calendar
    • Connections
    • Publishing
    • Inbox
    • Team
    • Account and team
    • Conversation
    • Memory
    • Questions
    • Media
    • Store
    • Plan
    • Orders
    • Activity

MCP

  • MCP server

Connectors

  • Brand connectors

Nödo and agents

  • Nödo in the brand

Genome

  • Genome specification
API/Brand API
Reference3 min read

Account and team

Your access, leaving, ownership and closing: explained here, confirmed on their own screen.

On this page
  • account.access.read · Your access
  • account.lifecycle.review · What would happen if…

Updated on January 1, 1970

Русский
한국어
日本語
中文
हिन्दी
Open the app
Previous
Team
NextConversation

In this section

  • Permissions and roles
  • Brand
  • Genome
  • Brand Kit
  • Library
  • Works
  • Calendar
  • Connections
Can't find what you need? Write to usWrite to usGo to the app
© 2026 Nömad · Nömad documentationLinkedInInstagramFacebookTikTokYouTubeX
Go to nomad.oooBack to top

On this page

  • account.access.read · Your access
  • account.lifecycle.review · What would happen if…

Read-only in every door.

account.access.read · Your access

Who the caller is around this brand: their role in the brand and in the workspace that holds it, the workspace owners, how many people have access, and which account and team changes their role lets them start here (operations: leave, remove someone, transfer ownership, close the brand or the workspace, delete the account). Every one of those is confirmed by the person on its own screen; use account.lifecycle.review to see what one would do.

FieldValue
KindRead
HTTP methodPOST /api/v1/account.access.read
MCP toolaccount_access_read
Scopeaccount.read
Minimum roleViewer
Human confirmationNo
DoorsNödo, Voice, MCP, API, Chat
StatusAvailable
Widgetrecord

Input

{}

Output

{
  role: "owner" | "admin" | "billing" | "member" | "viewer" | null  // Brand role of the caller, or null for Nömad staff.
  workspace: {
    id: string  // uuid
    name: string | null
  }
  workspaceRole: string | null  // Role in the workspace (owner, admin, billing, member, viewer), or null when access comes from the brand only.
  owners: string[]  // Names of the workspace owners: who can close, transfer or delete for everyone.
  people: {
    brand: integer  // -9007199254740991–9007199254740991
    workspace: integer  // -9007199254740991–9007199254740991
  }  // People with access to this brand and active in its workspace.
  operations: Array<"account.delete" | "workspace.close" | "workspace.transfer" | "workspace.leave" | "workspace.member.remove" | "brand.close" | "brand.leave" | "brand.member.remove">  // Changes the caller’s role allows starting here; a review says whether something blocks them now.
}

account.lifecycle.review · What would happen if…

Use it whenever the person asks about deleting their account, closing or leaving this brand or its workspace, transferring workspace ownership or removing someone. Pass operation; for a person, targetUserId or the name they typed in targetName (matched against the people with access here). Returns what would happen for this caller right now: allowed, blocker codes, decisions still to take on the screen (close_when, new_owner, workspace_successor), localized summary and details lines to explain in plain words, and href, the confirmation screen the card button opens. It never performs the change: the person confirms on that screen after a recent sign-in and, for irreversible changes, typing the name. Never say it is done. When allowed is false explain the blockers; permission_denied means only the people in owners can do it, and target_required means you should ask who among candidates.

FieldValue
KindRead
HTTP methodPOST /api/v1/account.lifecycle.review
MCP toolaccount_lifecycle_review
Scopeaccount.read
Minimum roleViewer
Human confirmationNo
DoorsNödo, Chat
StatusAvailable
Widgetrecord

Input

{
  operation: "account.delete" | "workspace.close" | "workspace.transfer" | "workspace.leave" | "workspace.member.remove" | "brand.close" | "brand.leave" | "brand.member.remove"  // The change the person asks about; account.delete is always about the caller.
  targetUserId?: string  // uuid · The person to remove, or who receives the workspace.
  targetName?: string  // ≤ 120 · The name the person typed («Ana»), when there is no id.
}

Output

{
  operation: "account.delete" | "workspace.close" | "workspace.transfer" | "workspace.leave" | "workspace.member.remove" | "brand.close" | "brand.leave" | "brand.member.remove"
  title: string
  allowed: boolean
  blockers: string[]  // Codes such as owner_must_transfer, paid_work_pending, target_required, permission_denied.
  decisions: string[]  // What the person still chooses on the screen.
  summary: string[]  // Localized headline lines, blockers first.
  details: Array<{
    title: string
    lines: string[]
  }>  // Localized lines by topic: people, works, plan, connections, what is kept.
  target: {
    id: string  // uuid
    name: string
  }
  | null
  candidates: Array<{
    id: string  // uuid
    name: string
  }>  // People to choose from when the target is missing or ambiguous.
  owners: string[]  // Who can do it, when the caller may not.
  href: string  // In-app path of the confirmation screen.
  requiresRecentSignIn: boolean
  requiresTypedConfirmation: boolean
}