Skip to content

Search documentation

Find a documentation page by the words on it.

Documentation

How Permissions and Feature Flags Limit the Agents

The agents never have more power than the person using them. Two things decide what an agent can do for you in a given chat: your role in the clinic, and the features Serelora has turned on for the clinic. This page explains how, so you know where to look when an ability is missing.

Your role comes first

Each ability the agent has is tied to a permission, the same one the matching screen needs. If you could not do something by hand, the agent cannot do it for you.

  • Offered or not. Before the agent starts, Serelora removes every ability your role does not allow. The agent is never shown them, so it does not offer them or promise them.
  • Checked again when it acts. Each time the agent uses an ability, the permission is checked again. A refusal is recorded in the audit log.
  • Approval does not add permission. When you approve a card, the change is made under your own account and checked against your permissions again. If you lost a permission after a card was prepared, the card opens without its approve button, or with a notice.

A clinic admin sees and changes what each role can do in Roles and Permissions and Custom Roles and Per-User Permissions. You can read the default for each ability in Everything the Agents Can Do.

Then your clinic's features

Some abilities exist only in clinics that have a feature turned on. A feature never grants a permission. It only decides whether the ability exists for the clinic. Only Serelora can turn a feature on, and a clinic cannot do it for itself. See Feature Flags for how to ask.

Feature What the agent loses without it
Encounters Reading a patient's visits
Orders Looking up and proposing orders
Billing Charges, invoices, payments, payment links and the billing summary
Patient messaging Texting a patient, and sending intake campaigns. Secure messages need its Secure messaging option
Skills Loading, drafting and editing skills
MCP connections Your connected outside tool servers
Code generation The offer to generate codes for a chart
Practice Agent The whole Practice Agent, and every tool in it
Population sub-agents Per-patient chart review runs

If the feature is off, the agent does not offer the ability. If it was asked for anyway, the answer reads "that feature isn't enabled for this clinic." See AI Agent Features Not Available for the messages you may see.

Role before feature

If you lack both, Serelora tells you about your role and never about which features your clinic has. That way a refusal does not disclose how your clinic is set up.

What this means in practice

  • Two people, two chats. A Physician and a Medical Assistant working in the same chart see different abilities. That is expected.
  • Same rules everywhere. The Serelora Provider phone app follows the same permissions and features. Cards that open on the web need the same rights there.
  • Plans and skills add nothing. A plan only sets the order of work, and a skill is a written procedure. Neither can give the agent an ability you lack.
  • Background runs. A per-patient review run uses the permissions of the person who started it, and no more.
  • The model you pick changes nothing here. See Choosing a Model for the Chat.

If something is missing

  1. Check your role in Roles and Permissions or ask a clinic admin.
  2. Check whether your clinic has the feature. See Feature Flags.
  3. Check that you are working in the clinic you expect. See Switching Between Clinics.