Invite your team
Add teammates to your organization, give them roles, and manage who has access.
Teammates each sign in with their own Lahuta account and work in the same dashboard. You decide what each person can do by giving them a role. At Northside Pottery, the owner might be an admin, while the studio assistant who answers customer messages is a member.
Roles
Every organization has two built-in roles, admin and member. Your organization can have roles of its own too. Someone with more than one role can do everything each of their roles allows.
Admins can do everything in the organization, including managing the team.
Members work with your customers. They can read and edit everything in the CRM and marketing, including sending campaigns and newsletter editions and publishing workflows, but they can't change what you sell or how the organization is set up.
| Area | Admin | Member |
|---|---|---|
| Contacts, groups, notes and reminders | Edit | Edit |
| The Do not email list | Edit | Edit |
| Inbox threads | Edit | Edit |
| Campaigns, workflows, newsletter and templates | Edit | Edit |
| Events, products, coupons, services and blog posts | Edit | View only |
| Guest lists, product orders, service orders and website payments | Edit | View only |
| Checking guests in, fulfilling orders, delivering service work | Yes | No |
| Refunds | Yes | No |
| Bookings and social posts | Edit | No access |
| Express Page, organization settings and connected mailboxes | Edit | View only |
| Stripe, members and API keys | Edit | No access |
A member still sees the whole sidebar. Pages they can't use either show an error or refuse to save. In the Express Page editor, a member sees the page but can't save changes.
Each role is a set of permissions, like events:write or campaigns:send. Roles and permissions lists every permission and which roles have it.
Door staff need check-in
Checking guests in is a permission of its own, events:checkin, and the
member role doesn't include it. If someone will scan tickets at the door, give
them a role that does, such as admin.
Invite someone
Open Members
Go to Settings → Members. The page shows everyone in your organization and any invitations still waiting.
Send the invitation
Select Invite user. Enter their Email address, choose a Role, and select Invite.
They accept
They get an email with a link to finish setting up their account. Once they sign in, your organization appears in their organization switcher.
Opening Members and inviting people takes the members:manage permission, which admins have.
Manage people and invitations
Each row on Members has an actions menu:
- Edit role changes someone's role. Pick the role and select Save.
- Remove user takes someone out of the organization straight away. They lose access to the dashboard.
- Resend invitation sends a waiting invitation again, in case it got lost.
- Revoke invitation cancels an invitation that hasn't been accepted.
Leaving an organization
Anyone can leave an organization on their own. Open the menu under your name, select Account, go to the Organizations tab and select Leave next to the organization. To get back in, an admin has to invite you again.
An organization always needs at least one member, so the last person can't leave it. To close an organization for good, an admin deletes it from Organization settings.
Working together
Once your team is in:
- Mention a teammate in a note on a contact and they get a notification. See Notes and reminders.
- Assign a reminder to a teammate so it lands with them when it's due.
- Each person chooses which notifications reach their own email. See Notifications.
API keys
Settings → API keys is where admins create keys for connecting your own website or tools to Lahuta. Members can't open it. Each key can do only what you choose for it when you create it. If a developer builds on Lahuta for you, send them to Authentication.
AI assistants connected to Lahuta act with the roles of the person who connected them. See Organizations and permissions.