# Collaborate on a Launch

Invite another Proxima account to a launch, choose its permissions and wallet scope, and manage shared access.

> Source: https://docs.proxima.tools/live-settings/collaborate/
> Language: English
> Content version: sha256:34bad297a1641e0716fae48cc4a2373f12175f3ac8dce12c9b804a68fd228301

Use **Collaborate** in the Live Workspace header to share one launch without sharing your own login.

[Invite a collaborator to a launch · Enlarge video](https://docs.proxima.tools/media/demos/done-live-invite-dark.webm)

Invite a collaborator to a launch

1.  ## Open Collaborate
    
    Only the launch owner, or a member with permission to re-share it, can manage access.
    
2.  ## Choose how to invite
    
    **Username** sends an invitation to a specific Proxima `@username`. **Approval link** creates a link; opening it sends the owner a request, and reveals no launch data before approval.
    
3.  ## Choose a role
    
    -   **View only**: launch dashboard, history, and automation setups.
    -   **Read / Write**: available working actions except withdrawals, token transfers, re-sharing, and Dev key export.
    -   **Admin**: full available access, including the sensitive actions selected by the owner.
4.  ## Customize permissions
    
    Open **Custom permissions** to choose individual actions. Permissions are enforced by the server even when a control is hidden in the interface.
    
5.  ## Set wallet scope and duration
    
    For actions that use wallets, select the exact wallets. Enable future wallets only if the member should also receive access to wallets added later. Access has no expiry by default; choose a date when it must end automatically.
    
6.  ## Review and manage access
    
    The owner can approve or decline link requests, edit a member’s access, revoke an invitation, or remove a member. A recipient sees who owns the launch and can select **Leave** to give up access.
    

> **Warning**
> 
> **Withdraw**, **Send tokens**, re-sharing, and **Export dev key** are sensitive permissions. Read / Write does not include them. Key export applies only to an exportable Dev wallet key.

Shared access does not transfer ownership. The live chart and launch data remain owned by the original account.