Account and access

Work together without sharing a login

Give each person the access their role needs, while keeping account ownership clear.

Who this helps: Site Owners and Admins who manage collaborators.
Before starting: Ask the collaborator to create their own Webrenew account and confirm their sign-in email.
Done when: The intended collaborator can open the site with the correct role.

Add a collaborator

A site supports up to 10 collaborators in addition to its owner. Access is specific to that site.

Open Site overview → Collaborators. A person must already have a Webrenew account; entering an unknown address does not create one.

Confirm the email address used by the collaborator's account.
Add the address and choose Editor or Admin.
Check the resulting member list.
Ask the collaborator to open the shared site from their dashboard.

Adding an alert recipient under Forms is separate. An alert recipient does not automatically become a collaborator.

Choose the least access needed

Editor includes publishing, page editing, posts, and submissions. Admin also includes sensitive site settings such as email, domains, and service keys.

The following matrix comes from the permission rules used by Launch.

Launch site role permissions
Action	Owner	Admin	Editor
Edit pages, posts, and media	Yes	Yes	Yes
Publish changes	Yes	Yes	Yes
Change SEO, crawling, and custom code	Yes	Yes	Yes
See form submissions	Yes	Yes	Yes
Rename the project	Yes	Yes	Yes
Connect and remove domains	Yes	Yes	No
Turn analytics on or off	Yes	Yes	No
Choose who gets form emails	Yes	Yes	No
Manage email and follow-ups	Yes	Yes	No
Add and change environment variables	Yes	Yes	No
Add and remove collaborators, change roles	Yes	Yes	No
Duplicate the project	Yes	No	No
Start the AI chat over	Yes	No	No
See the first-steps checklist	Yes	No	No
Archive or delete the site	Yes	No	No

Understand the owner's responsibilities

The owner's plan governs the site's paid features. Site files count against the owner's storage allowance, including files uploaded by collaborators.

The owner controls account-level billing. Site ownership is distinct from an Admin role; making someone an Admin does not transfer the account.

Admin includes managing collaborators and service keys. Grant it only when that person needs those responsibilities.

Review access when work changes

Use Collaborators to change a role or remove access when a project ends. Keep one clearly identified owner responsible for the business website.

Review the collaborator list after a team or supplier change.
Change the role or remove access as appropriate.
Confirm the resulting list.
Review external-service access separately if that person also had access outside Launch.

← All guides