Collaborators and Workspace Access

Applies to: AppWizzy projects that support collaborators

A collaborator receives broad access to one AppWizzy project. AppWizzy does not provide separate fine-grained collaborator roles.

Review all project data and credentials before you add a collaborator.

What a collaborator can access

A collaborator can open the shared project from their AppWizzy account. The available pages and controls depend on the selected template.

Project access can include:

  • project overview and status.
  • supported editor or workspace interfaces.
  • project settings and service details.
  • activity, logs, and project billing records.
  • application URLs and shared workspace access.
  • SSH access and its management controls.
  • VM lifecycle controls.

Some credential controls remain unavailable to collaborators. For example, only the owner or an administrator can reveal application administrator credentials.

Only the owner or an administrator can rotate AppWizzy Codex Desktop passwords. The project owner controls membership and project deletion.

Access depends on the template

Project type Possible collaborator access
Hosted VM or runtime SSH, service URLs, VM controls, files, and stored credentials
AppWizzy Codex Desktop Remote Desktop, Codex, files, terminal history, browser sessions, and shared passwords
AppWizzy Codex Browser workspace, project files, sessions, and shared access password
Hermes Agent Dashboard, API access, workspace data, and shared credentials
App Generation Editor, schema, source tools, deployments, settings, and generated application data
Ready-made software Application, administrator access, settings, and template-specific data

The selected template guide identifies its access methods. Do not assume that a project collaborator has only read access.

Before you add a collaborator

Confirm these conditions:

  • The person has an AppWizzy account.
  • You use the email address from that account.
  • Your plan supports another collaborator.
  • The person needs broad project access.
  • You trust the person with project data and credentials.

The project owner needs an eligible paid subscription to add collaborators.

Add a collaborator

  1. Open the project.
  2. Select Collaborators.
  3. Enter the collaborator's AppWizzy account email.
  4. Select Add collaborator.

AppWizzy sends a notification to an existing user. The project then appears in that user's project list.

If the person has no account, ask them to register. Then repeat the procedure with their registered email.

Remove a collaborator

  1. Open the project.
  2. Select Collaborators.
  3. Find the user in the collaborator list.
  4. Select Remove.
  5. Confirm the removal.

Removal stops access through that AppWizzy account. It does not automatically replace every password, key, provider session, or application account.

Secure the project after removal

Complete these actions when a former collaborator could retain access:

  1. Rotate shared workspace passwords.
  2. Rotate or revoke project SSH access.
  3. Replace shared application passwords and API keys.
  4. Remove personal provider sessions from the VM.
  5. Revoke external repository or service access.
  6. Review recent project activity and billing records.

AppWizzy Codex Desktop can rotate its two workspace passwords together. Use project settings for the available credential controls.

Contact support when a template does not provide the required rotation control.

Billing responsibility

Collaborator actions can start resources, change a machine, or use paid services. These actions can affect charges for the project owner.

Remove access promptly when a person no longer works on the project.