> ## Documentation Index > Fetch the complete documentation index at: https://docs.tiro.ooo/llms.txt > Use this file to discover all available pages before exploring further. # Add or Update Workspace Member > Idempotently assign an existing organization member to an organization workspace, or update that workspace role. This endpoint does not create or invite users. ## OpenAPI ````yaml /openapi.yaml put /v1/external/organizations/me/workspaces/{workspaceGuid}/members/{userGuid} openapi: 3.1.0 info: title: Tiro API description: AI-powered note-taking and voice file processing API version: 1.0.0 contact: name: Tiro Support email: support@tiro.ooo url: https://tiro.ooo servers: - url: https://api.tiro.ooo description: Production server security: - BearerAuth: [] tags: - name: Note description: Operations for managing notes and their paragraphs - name: Note Share Link description: Manage share links for notes - name: Note Summary description: Operations for retrieving note summaries - name: Note Document description: Template-based document generation from notes - name: Note Document Template description: Operations for managing note document templates - name: Folder description: Operations for retrieving folders - name: Voice File description: Operations for voice file processing - name: Word Memory description: > Manage word memories to improve voice transcription accuracy. Register important terms like company names, people's names, and product names so Tiro recognizes them precisely during recording. Each term has an `entry` and an optional `subEntry` (an alternate spelling or notation). Personal (User), workspace-shared (Workspace), and organization-shared (Organization) word memories are managed separately, and each scope supports bulk create/update/delete (up to 1000 items per request). - name: Wiki description: | Access workspace wikis — unified knowledge graphs built from notes. Requires a workspace with wiki plan and activation enabled. - name: Organization description: > Endpoints for organization API keys. An organization key is issued by an organization admin, carries fixed scopes chosen at issuance, and can reach the notes in every workspace that belongs to the organization. Built for server-to-server integrations such as CRM sync — receive `note.ended` webhook events, generate documents for notes, and reconcile with the organization notes list. - name: Organization Management description: Operations for the authenticated user's organization. paths: /v1/external/organizations/me/workspaces/{workspaceGuid}/members/{userGuid}: put: tags: - Organization summary: Add or Update Workspace Member description: >- Idempotently assign an existing organization member to an organization workspace, or update that workspace role. This endpoint does not create or invite users. operationId: putOrganizationWorkspaceMember parameters: - $ref: '#/components/parameters/WorkspaceGuid' - $ref: '#/components/parameters/UserGuid' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PutExternalWorkspaceMemberRequest' responses: '204': description: Workspace membership is in the requested state '400': description: Invalid role or request body content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Invalid or non-organization API key content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: >- Missing `organization_member:write` scope or workspace belongs to another organization content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Workspace or organization member not found content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: >- The requested seat-consuming role would exceed the workspace seat limit content: application/json: schema: $ref: '#/components/schemas/Error' components: parameters: WorkspaceGuid: name: workspaceGuid in: path required: true description: Workspace GUID schema: type: string UserGuid: name: userGuid in: path required: true description: User GUID schema: type: string schemas: PutExternalWorkspaceMemberRequest: type: object required: - role properties: role: type: string enum: - ADMIN - MEMBER - VIEWER description: >- ADMIN can manage the workspace; ADMIN and MEMBER consume a seat and can record; VIEWER is read-only, consumes no seat, and cannot record. Error: type: object required: - error properties: error: type: object required: - code - errorType - message properties: code: type: integer description: > 6-digit error code in `AAABBB` form: first 3 digits match the HTTP status, last 3 digits are a per-status serial (e.g. `404018`). Use only when you need to distinguish specific error cases within the same HTTP status — values may be added or renumbered across releases. For general client branching, prefer `errorType`. example: 404018 errorType: type: string description: > Stable, coarse-grained error category. Recommended default for client-side branching: the value-to-status mapping is part of the API contract and will not change without a breaking-change notice. Typical use: - `unauthorized` → trigger re-authentication - `forbidden` → surface a permission error to the user - `not_found` → treat as missing resource - `too_many_requests` → back off and retry - `internal_error` → retry with exponential backoff enum: - bad_request - unauthorized - forbidden - not_found - not_acceptable - conflict - payload_too_large - unprocessable_entity - too_many_requests - internal_error example: not_found message: type: string description: >- Human-readable error message. Not stable; do not use for branching. example: 'No team found for user #217' detail: type: string nullable: true description: Additional error details example: null securitySchemes: BearerAuth: type: http scheme: bearer description: API key in format {id}.{secret} ````