# Add Collaborators from the Dashboard

Invite people to a LunaSites project from the Dashboard, choose appropriate access, and refine page-level editing permissions in the site editor.

# Add Collaborators from the Dashboard

Add collaborators from the selected site’s Dashboard settings, then keep their site role distinct from page locks and release ownership. Confirm the intended person and responsibility before sending an invitation.

## Open Settings → Collaborators

From the Dashboard, select the exact site, open Settings, and find Collaborators. The prepared image uses a privacy-safe empty test site so no private email addresses or production collaborator records are exposed.

![Privacy-safe Luna Dashboard Collaborators panel with email field, Administrator scope, and Invite control](https://lunasites.io/api/luna-gallery/1785863595531-sv5kd4-01-collaborators-invite-empty-test-site.jpg/@@images/image)

## Invite an Administrator

1. Enter the invitee’s email address. 2. Review suggestions carefully; they may include people who accepted an earlier invitation. 3. Press Enter or choose Invite. 4. Confirm that the invitation moves from Pending to Active before relying on access.

## Understand the limits

The invitation shown grants Administrator scope for content and publishing. Administrators do not receive owner-only billing or site-deletion authority. Ownership transfer and other owner-only account actions remain separate from ordinary content collaboration.

## Keep page access and locks separate

After site access is active, apply the narrowest useful page or parent scope where the editor exposes Sharing. A collaborator role does not take over a page that another editor currently owns; coordinate the edit request or handoff instead.

## Offboard without exposing private data

Confirm the exact collaborator record, communicate the end of access, and use the owner-controlled removal flow. Review inherited or page-specific sharing separately, and do not place real email addresses in public documentation, captions, screenshots, or troubleshooting examples.

## Responsive and accessibility checks

On smaller screens, confirm that invitation fields, suggestions, statuses, and actions remain inside their cards. Use keyboard navigation, keep focus visible, read Pending or Active text rather than color alone, and confirm any destructive removal.

## Invitation checklist

Correct site. Correct email. Intended Administrator responsibility. Suggestion verified. Enter or Invite used once. Pending monitored until Active. Owner-only limits understood. Page scope tested. Offboarding plan recorded.

## Next steps

Read Multi-User Editing before the collaborator opens an active page, then define the save, review, and publish owner in Content Workflow.