Invite teammates and manage permissions
Invite the right people, assign project roles and site work permissions, and check editor seat limits.
Understand the two permission levels
Neopress separates a person's project role from their site work permissions. A project role determines access to administration, while site work permissions determine the changes a member can make. Opening a project does not automatically grant permission to edit or publish it.
- Owner: manages the project, billing, team access, ownership-level changes, and site deletion.
- Admin: manages site settings and site work, plus Members and Viewers. Billing and Owner/Admin management remain with the Owner.
- Member: works on the site according to the individual permissions assigned.
- Viewer: can browse the permitted workspace without changing it and does not use an editor seat.
Invite a teammate
- Open the project's team settings and choose Invite member.
- Enter the intended teammate's email address.
- Select a project role. Only the Owner can invite an Admin.
- For a Member, choose an appropriate preset or the individual site work permissions shown.
- Check the editor seat information and send the invitation.
- Review the pending invitation and confirm membership after the recipient accepts.
Use the smallest set of permissions the teammate needs. A person writing articles may not need authority to change site settings, publish the entire site, or perform destructive actions.
Check editor seats
Launch includes one editor seat per site, and Growth includes ten. Viewers do not count toward those limits. The team screen shows the current usage. When editor seats are full, an invitation can be sent as a Viewer; check the resulting role rather than assuming the requested editing access was granted.
Each client site or project has its own membership and plan. Access to one project does not provide access to every other project in the account.
Update or remove access
Open the member's access controls to change the role or site work permissions, then save. The available choices depend on your own role and the site's plan. Revoke a pending invitation if it should no longer be accepted. Remove a member when they no longer need access to the project.
When a teammate cannot complete a task
Check the project they opened, whether their invitation was accepted, their current role, the relevant site work permission, and the plan. Publishing and connected external tools can enforce additional role requirements. An MCP connection uses the connected person's access; it does not grant new project permissions.