Members & roles
Coco CRM is multi-user: everyone works in the same workspace, and roles control what each member can see and change.
Inviting members
Public sign-up is disabled on Coco CRM — accounts are created by invitation only.
- Go to Settings → Members.
- Click Invite member and enter the person's email address (or copy the invite link).
- The invitee receives an email, follows the link, and sets up their account.
The Members page lists everyone in the workspace with their role. Admins can change a member's role or remove members from the same page.
Signing in
Members sign in at crm.cocolevio.com with either:
- Email and password — click Continue with Email.
- Microsoft Entra ID SSO — sign in with your Microsoft work account; no separate password to manage.
Both methods lead to the same account if the email matches. Because sign-up is disabled, an uninvited email cannot create an account through either method.
Roles and permissions (RBAC)
Every member has exactly one role. Roles are managed in Settings → Roles, where admins can edit the built-in roles or create new ones.
A role bundles two kinds of permissions:
Object permissions
Per object (Companies, Deals, Leads, any custom object), a role grants or denies:
| Permission | Allows |
|---|---|
| See | Viewing records and their views |
| Create | Adding new records |
| Update | Editing existing records |
| Delete | Deleting records |
Use this to, for example, give a contractor read-only access to Companies while hiding Deals entirely. Objects a member can't see disappear from their sidebar, search, and dashboards.
Settings permissions
Per settings area, a role controls whether the member can manage:
- Data model — objects and fields
- Workflows — automation
- Members and roles — invitations and RBAC itself
- API keys and webhooks
- Workspace settings — name, security, apps
Admin vs member
In practice most teams use two roles:
- Admin — full object access plus all settings: invite members, edit the data model, manage apps and API keys.
- Member — full or scoped access to CRM records, but no settings management.
You can refine from there — e.g. a Sales role with full Deals/Leads access but no delete rights on Companies.
Good practices
- Keep at least two admins so the workspace is never locked out.
- Grant settings access sparingly — data-model and workflow changes affect everyone.
- When someone leaves, remove them in Settings → Members; their records and activity history remain intact.
Related: Objects and Fields for what data-model access controls, and API and Webhooks for API-key management.