Security & trust
Roles and access
Who can see and do what in Fido: five roles, module permissions for schedulers and staff, the access limits on the assistant and API keys, and how to turn a person's access off.
Every person in a Fido organization has a role. The role decides which portal they use and what they can see and do there.
The five roles
| Role | Who | Portal |
|---|---|---|
| Admin | The organization's owner or owners | Organization portal, with every module |
| Scheduler | Staff who book and fill work | Organization portal, within the permissions an admin sets |
| Client | The customer who requests service | Client portal |
| Consumer | The person who receives the service | Consumer portal |
| Provider | An interpreter or other service provider | Provider portal |
An organization can have more than one administrator.
What each role sees
- A client sees its own requests, assignments, consumers, locations and invoices. A client sees which providers are assigned. Provider pay stays between the provider and the organization.
- A consumer sees its own schedule and the provider details for its assignments. A consumer sees no billing or pay.
- A provider sees its own offers, schedule, payables and payment statements.
- A provider's hover card in a portal shows the name, photo and credentials of providers on that person's own work, and of providers linked to them by a preferred or restricted list. Contact details show to organization staff and to the provider on their own card. Pay rates and estimated pay show to staff who have Finance Read.
- Clients and consumers see an assignment after it is confirmed, and each role sees the information it needs to take part.
- History & Logs shows clients, consumers and providers the actions they took themselves.
See The four portals.
Permissions for schedulers and staff
Admins set what schedulers and other staff can do in each module. For each module, an admin chooses from four actions:
| Action | What it gives |
|---|---|
| Read | See lists and records, and export |
| Write | Create records |
| Edit | Change records |
| Delete | Delete records |
The modules are Schedule, Assignments, Shifts, Handshakes, Clients, Consumers, Providers, Team, Finances, Forms, History & Logs and Settings.
- Choosing any action also gives Read.
- Removing Read hides the module from that role.
- An admin sets one permission map for a role, so everyone in the role works the same way, and can then fine-tune an individual person.
- Admin accounts keep access to everything, so an organization always has access to its own settings.
- Each permission change is written to History & Logs with the earlier and new value.
A refusal names the missing action, for example "You do not have permission to Edit Finances."
Who signs in
Admins and schedulers sign in with their account. Clients, consumers and providers also need Portal Access turned on and an Active status on their record. People can sign in with email and password, or with Google or Microsoft when the organization turns that on.
Who works with whom
Each organization, client and consumer can keep a preferred list and a restricted list of people. Preferred providers go first in the picker and in every broadcast. Restricted providers are left out of both. An admin or scheduler can set the lists from a record, from Settings > Preferred Users and Restricted Users, or for one assignment, and a scheduler can override a restriction. See Preferred and restricted providers.
The assistant, the connector and API keys
The built-in assistant, AI apps connected through the connector and organization API keys all work within the permissions of the person they act for.
- Assistant. It acts as the signed-in person, and every change waits for a confirmation.
- Connector. AI apps such as Claude and ChatGPT act as the signed-in user, role-scoped. Admins turn AI app access on or off for the client, consumer and provider roles in Settings > AI Tools, and removing a connector key disconnects the app.
- API keys. An admin or scheduler creates a key in Settings > API Keys, and the key is shown once. A scope has a module and an action, such as
assignments:read, and a request works when the scope and the key owner's role both allow it. Each key carries an expiry, a rate limit and an optional IP allow-list, and can be rotated or revoked.
Turn access off
Change a person's status to Inactive or Suspended and Fido turns off their portal access. The record, its assignments and its history stay in place. Setting the status back to Active, with Portal Access on, restores sign-in. Fido checks status and Portal Access each time a provider, client or consumer uses the portal, so a change applies on their next action.
How it works
One sample job, step by step: what you see, and what Fido does behind it.
SampleLincoln ISD · client user · invite
- Day 1What you see: Dana K. invites a Lincoln ISD client user. The list shows the chip Invited.What Fido does: Each login shows Not invited, Invited, Invite expired, No sign-in yet or Active, with a one-line explanation.
- Day 7What you see: The client user missed the email, and the chip reads Invite expired.What Fido does: Invites last seven days by default.
- Day 8What you see: Dana opens the row menu and selects Resend invite.What Fido does: A fresh link goes out. Each person can be sent a new link every five minutes.
- Day 8What you see: The user signs in, and the chip changes to Active.What Fido does: Once someone has a password, the action becomes Reset password and sends a reset link. Only one shows at a time.
- LaterWhat you see: A provider's email is delayed, so Dana sets a password for them.What Fido does: Fido logs who set it and can optionally email the person.
Related
Review access settings with the Fido team
A live walkthrough built around your kind of work.