Organizations and permissions
Choose which of your organizations the assistant works in, and see what your role lets it do there.
Your assistant always works inside one of your Lahuta organizations, and it can only do what your role in that organization allows. This page covers how it picks the organization, how to point it at another one, and what admins and members can each do.
The default organization
When you sign in while connecting an assistant, Lahuta asks which organization to connect if you belong to more than one. If you belong to only one, it's picked for you. That organization is the default for the connection: every request goes there unless you say otherwise.
Not sure where the assistant is working? Ask it: "Which Lahuta organization are you using?" It checks with the orgs_current tool, which returns the organization's name and slug and your role there.
To change the default, disconnect Lahuta in your assistant, connect it again, and choose the other organization when you sign in.
Work in another organization
You don't have to reconnect to use a different organization. Every Lahuta tool takes an optional org setting, the organization's slug or id, and the assistant fills it in when you name the organization:
- "In northside-pottery, list next week's events."
- "Act in northside-pottery for the rest of this chat."
- "Show me upcoming events in each of my organizations."
The slug is the last part of your dashboard address. For lahuta.org/dash/northside-pottery, it's northside-pottery. You can also ask "Which Lahuta organizations am I in?" and the assistant lists them with the users_list_orgs tool, most recently opened first.
The choice applies call by call. If an answer looks like it came from the wrong place, ask the assistant which organization it used for that step.
Only your own organizations
The assistant can reach an organization only if you're a member of it. Naming one you're not in, or a slug that doesn't exist, gets the same "not found" answer, so the reply never reveals whether an organization exists.
What each role can do
Your role in each organization decides what the assistant can do there. The same person can be an admin at one studio and a member at another, and the assistant follows the role of whichever organization it's working in.
Admins can use every tool. Members can look up most things and work with contacts and marketing, but can't manage events, bookings, the shop, services, the blog or social posts.
When the assistant is refused, the error names the missing permission, like events:manage. This table shows what each permission covers.
| Permission | What it covers | Admin | Member |
|---|---|---|---|
crm:read | Looking things up: contacts, groups, notes, reminders, the inbox, campaigns, the newsletter, templates and sequences. Also read-only views of events, registrations, tickets, check-in, co-hosts, products, collections, shop orders, services, custom offers, service orders, blog posts, your file library and your team. | Yes | Yes |
crm:write | Adding and changing contacts, groups, notes and reminders. Replying to, closing and assigning inbox threads. Drafting, scheduling and cancelling campaigns and newsletter editions. Managing newsletter topics and subscribers, templates and sequences. | Yes | Yes |
events:manage | Creating and changing events, dates, tickets, guests, approvals, check-in, event messages, co-hosts and registration form questions. | Yes | No |
bookings:manage | Everything to do with bookings, including looking them up: booking pages, open times, booking, marking and cancelling. | Yes | No |
commerce:manage | Creating and changing products, variants, photos, collections, services and custom offers. Fulfilling and cancelling shop and service orders. Everything to do with coupons, including looking them up. | Yes | No |
blog:manage | Writing, publishing, unpublishing, reviewing and deleting blog posts. | Yes | No |
social:manage | Everything to do with social posts, including looking them up. | Yes | No |
org:manage | Checking your Stripe payment connection. | Yes | No |
A few things stand out for members. They can see events, orders and services through the assistant, but not change them. Coupons, bookings and social posts are admins only, even to look at. And members can send campaigns and newsletter editions, since those fall under crm:write.
Some tools add a rule of their own. For example, only the person who wrote a note can edit or delete it, whatever their role. The Tools reference lists who can use each tool.
When your role doesn't allow something
If the assistant tries a tool your role doesn't cover, Lahuta refuses it and changes nothing. The assistant gets an error with the reason Forbidden and the missing permission, and a good assistant tells you so rather than guessing.
| The assistant reports | What it means | What to do |
|---|---|---|
Forbidden with a permission like events:manage | Your role in that organization doesn't include it. | Ask an admin to do it, or to change your role. |
NotFound for resource: organization | The slug or id is wrong, or you're not a member of that organization. | Check the slug in your dashboard address, or ask for your list of organizations. |
Lahuta checks your role on every call, not only when you connect. When an admin changes your role, the assistant follows the new role without you reconnecting. Admins manage roles in the dashboard, as described in Invite your team.