VELORYZ STUDIO / KNOWLEDGE

Manage users and workspaces

Account lookup, membership and support-safe actions.

Manage users and workspaces

VELORYZ Studio · Administration and governance Audience: Authorised Studio administrators and policy owners Guide type: Practical Studio operations guide

Purpose

Manage users and workspaces 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. Account lookup, membership and support-safe actions.

This guide covers account lookup, membership and support-safe actions. 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

Studio Control at /admin manages public site content, projects, campaigns, media, AI provider settings and publication history. Some governance functions in the blueprint, including elaborate reviewer roles and automated review scheduling, are not verified capabilities.

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 valid owner session, scoped change request and rollback plan
  • Accurate contact, brand, project and policy information
  • A record of which changes should become public
  • A short list of measurable success criteria specifically for manage users and workspaces.
  • 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 Manage users and workspaces: 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

These steps apply to Manage users and workspaces. The implementation must be verified against the current Studio permissions, deployed provider connections and approved project scope.

  • Treat owner admin authentication and project client portal authorization as distinct flows.
  • Document what account management is truly available; do not invent team role controls or ownership transfer UI.
  • Use least-privilege access and avoid sharing password gates with clients.
  • Review removal and account recovery procedures with the authorised operator.

Evidence to retain

  • The original input or situation, and a clear before/after comparison.
  • The reviewed version, responsible owner and acceptance record.
  • Any limitation, follow-up decision, or safely reversible workaround.

Configuration and decision points

  • Sign in through the protected Studio Control flow; avoid sharing owner credentials.
  • Edit approved content in the appropriate CMS section and save draft before publishing.
  • Preview draft changes, publish intentionally and inspect the public result.
  • Use history and restore for documented corrections while preserving operational accountability.

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

  • An unauthorised user cannot access owner settings or export secrets.
  • Draft changes are not publicly exposed before publication.
  • Documentation and legal copy match approved current policies.
  • Version history and restoration are tested with representative changes.

Also confirm that the result addresses the original objective: Account lookup, membership and support-safe actions.. 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 authorization fails, verify the approved sign-in method rather than bypassing controls.
  • If an edit overwrites another revision, reload the newest version and reconcile.
  • If a publication is incorrect, use the owner restore path and republish after review.

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

  • [Studio administration overview](/docs/studio/admin/overview/)
  • [Plans, entitlements and usage controls](/docs/studio/admin/plans-usage/)
  • [Documentation CMS and publishing](/docs/studio/admin/docs-cms/)
  • [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.

Let’s talk
Make your project