Invite and remove members
Invites, acceptance, removal and ownership transfer.
Invite and remove members
VELORYZ Studio · Workspace and project management Audience: Studio owners, project coordinators and customers using the client portal Guide type: Practical Studio operations guide
Purpose
Invite and remove members should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Invites, acceptance, removal and ownership transfer.
This guide covers invites, acceptance, removal and ownership transfer. Use it as an actionable practical studio operations guide: verify the current UI and any provider configuration before relying on a control in production.
Availability and responsibility
The working site includes a protected /admin workspace, enquiries, project management and a separate client portal. The repository does not establish a general customer-facing member and role editor; do not invent invitations, ownership-transfer controls or self-service archive options.
Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.
Before you begin
- A project brief, unique project reference and named coordinator
- Agreed team responsibilities and access requirements
- A change request log and approval contact
- A short list of measurable success criteria specifically for invite and remove members.
- A recovery plan if the proposed change creates a regression.
Recommended procedure
- Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
- Define the specific work item for Invite and remove members: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
- Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
- Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
- After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.
Topic-specific operating procedure
The following steps are specific to Invite and remove members and supplement the general workflow above. Apply only the controls and roles actually available to your account or deployment.
- Identify the intended participant, project reference and permitted actions before sending an invitation.
- Use the actual client portal invitation process rather than assuming arbitrary workspace invites exist.
- Avoid including sensitive invitation codes in screenshots or public logs.
- Test both successful acceptance and invalid/expired invitation behavior.
Evidence to retain
- A short before/after record of the actual user-visible change or reviewed deliverable.
- The exact site URL, owner or reviewer, and the approval or release reference.
- Any unresolved limitation, assigned follow-up, and a safe mitigation.
Configuration and decision points
- Create or request project work via /create/, and record the reference for later communication.
- Studio owners use /admin to manage project records and published content; customers should use /client/ only when invited.
- Separate customer-visible status updates from private admin notes and credentials.
- Record changes to scope, roles and delivery milestones before implementing them.
When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.
Verification checklist
- Projects and client messages are associated with the correct reference.
- Owner-only data stays behind authentication and customers see only authorised content.
- A project is not deleted or marked complete without an agreed recovery path.
- All invitations and access removals are documented by the responsible administrator.
Also confirm that the result addresses the original objective: Invites, acceptance, removal and ownership transfer.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.
Troubleshooting and recovery
- If a client portal invitation fails, request a corrected invitation instead of guessing codes.
- Do not share passwords, session cookies or API keys in support conversations.
- For accidental publication changes, use owner-controlled CMS draft, version history and restore processes.
When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.
Related reading
- [Workspace overview](/docs/studio/workspace/overview/)
- [Create and manage projects](/docs/studio/workspace/projects/)
- [Workspace settings](/docs/studio/workspace/settings/)
- [All VELORYZ documentation](/docs/)
- [Studio documentation](/docs/studio/)
- [Help Centre](/help/studio/)
- [/create/](/create/)
- [/docs/client-portal/](/docs/client-portal/)
Operational note
This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.
