Skip to content
plugboard.appRequest a demo

Reference

Permissions

The complete set. Permissions are granted through roles, and a role holding * is a superuser within its tenant.

The same checks run on the web console, the REST API, the MCP server and Ask.

KeyAllows
loan.viewSee loans and who has what
loan.issueIssue a loan device
loan.returnMark a loan returned
loan.manageRegister devices, edit, bulk actions, manage loan groups
KeyAllows
device.viewSee device records and history
device.manageSend MDM commands, other than wipe
device.wipe.requestRequest a device wipe
device.wipe.approveApprove a requested wipe and make it happen
device.laps.readRead a device’s local administrator password
induction.manageRun inductions, import rosters, record issued devices
KeyAllows
repair.viewSee submissions
repair.createLodge one
repair.updateChange non-closing status, priority, assignment, add notes, record outcome and cost
repair.closeClose or delete one
KeyAllows
ticket.viewSee tickets, their logged time, and My time
ticket.createRaise one, including by making quick time into a ticket
ticket.updateChange non-closing status, queue, assignment. Also log time, run timers, set an estimate, and edit or delete your own time; escalate and de-escalate a ticket between support tiers, with the reason kept in its history; choose the supplier a ticket is with; choose the service a ticket is filed under; and hand a security incident to Security, which needs no other key
ticket.commentReply publicly
ticket.internalRead and write internal notes
ticket.closeClose one
ticket.ingestReceive whole-school mailbox deliveries through an API key: create tickets, add public replies and attachments, and resume waiting tickets on requester replies

Mail intake keys require an unrestricted campus grant. ticket.ingest authorises routing to enabled, licensed departments through configured mailbox addresses; it grants no general department reading API. Default read-only keys and ordinary ticket write permissions do not authorise intake. Create a dedicated key with ticket.ingest using an account that holds it (or an Owner), then configure that key in the mail gateway. Like every API key, it stops working while API and webhooks (module.integrations) is off.

A transition to closed through generic edits, actions, bulk operations and external tools requires the relevant close permission. Closing during a merge also requires ticket.close. Editing metadata on an already closed item and reopening it still need only the update permission.

These controls apply when the school is entitled to a department add-on.

KeyAllows
departments.manageSchool-wide department administration and membership changes, while retaining campus bounds
ticket.transferTransfer a ticket, also requiring ticket.update and access to both departments

Department membership limits which tickets a staff account can access. Existing ticket action permissions still apply. The restriction that removes legacy ICT access is explicit; broad department administration should not be granted to a department-only worker. Once departments exist, shared ticket/workflow settings also require departments.manage alongside their existing permission. See school departments.

KeyAllows
stock.viewSee stock levels and items, and the supplier records
stock.manageMaintain the catalogue and sell items; add, edit and delete suppliers and choose their repair vendor connector
cost.viewSee cost analytics
cost.exportExport cost data
cost.manageCreate, edit and delete cost reporting terms
software.viewRead the software contract register; licence-position reports also require identity.view
software.manageCreate, edit and delete software contracts and configure renewal email recipients
charge.viewSee damage charges
charge.raisePropose a charge
charge.approveApprove, decline or waive a charge

Supplier records use the stock keys. Setting a device’s supplier needs device.manage, a ticket’s ticket.update, and choosing the software contracts a supplier holds software.manage.

KeyAllows
client.viewSee people and their profiles; also opens Ask
client.manageEdit person records, register cards
people.whereabouts.viewSee where a student is timetabled right now. Every look is recorded in the audit log. A staff member’s timetable needs only client.view
directory.viewSearch the identity provider: the Accounts view of People, and Search all accounts on a person’s page. With client.view, either one shows People in the navigation
directory.manageChange licences, enable or disable, delegate and reset passwords on demonstration directory accounts; also link accounts, manage directory requests, and plan group and organisational unit changes

Reads, then writes, against a person’s identity provider account. These are split from directory.* because they reach sign-in history and account state for staff and children.

KeyAllows
identity.viewSee identity provider state for a person
identity.signins.viewSee sign-in history (IP address, city and device) for a person
identity.policy.viewSee identity policy, such as MFA requirements, for a person
identity.mfa.resetReset a person’s MFA
identity.account.manageDisable a person’s identity provider account
identity.account.enableRe-enable a disabled identity provider account
identity.session.revokeRevoke a person’s active sign-in sessions
identity.license.manageAssign or remove a person’s identity provider licence, on the person’s Account tab or a live Entra account in the Accounts view, with a typed name, a reason and fresh authentication
identity.password.resetReset a person’s identity provider password
identity.mailbox.delegateRevoke direct mailbox delegation, with step-up and a reason; live Send As grants are blocked
identity.mailbox.fullaccessAlso allow granting Full Access, together with identity.mailbox.delegate
identity.tap.issueFrom 0.55.0, issue a Microsoft Entra Temporary Access Pass: a working sign-in that lasts eight hours and can be used once. Up to 10 an hour for each person. Never for an account with a directory role, or one whose Plugboard user holds permissions you do not. See Temporary Access Passes

Unlocking an account in account recovery uses identity.account.enable, resetting a password identity.password.reset, and resetting MFA or issuing backup or bypass codes identity.mfa.reset.

identity.tap.issue is its own key and is never implied by identity.mfa.reset. No built-in role other than Owner holds it, so a school that issues passes grants it to the roles that should. Without it, a joiner plan’s pass step is refused.

identity.account.enable is a separate key on top of identity.account.manage. Disabling an account is the reversible, low-stakes off-boarding action wanted at the desk; re-enabling one restores access to a leaver’s mailbox and is the harder direction to grant.

KeyAllows
user.manageCreate and deactivate staff accounts
site.manageCreate campuses, and set which campuses a person administers
role.manageCreate roles and change what they hold
connector.manageConfigure connectors and credentials
assistant.agentforce.useUse a separately enabled Salesforce Agentforce advisory connection in the Ask panel; also requires client.view and Integrations. Salesforce execution-user permissions determine remote data access
branding.manageChange name, logo and colours. From 0.49.0 also the email design and the school’s own email templates
dashboard.managePublish, update and remove shared team dashboard templates. Personal saved views need no grant
dashboard.link.manageCreate and revoke wall-screen links to dashboards. A link shows a dashboard on a screen nobody signs in to, so it is kept apart from dashboard.manage
feature.manageEnable and disable modules
workflow.manageStatuses, priorities, types, coverages, parts. From 0.17.1 also the time tracking settings, and editing or deleting anybody’s ticket time and quick time
billing.manageEnter or remove a licence key
integration.manageIssue API keys, manage webhooks
audit.viewRead the audit log
KeyAllows
monitor.viewSee service monitors
monitor.manageCreate and configure monitors
dns.viewSee DNS record history and the DNS dashboard cards. The DNS monitors themselves use monitor.view and monitor.manage
network.viewSee the network estate: switches, access points, uplinks
network.clients.viewSee where a device was last seen on the network
network.config.viewFrom 0.21.0, read stored network configuration snapshots and the differences between versions, on the Configuration tab of Network
network.diagnoseRun network checks (ping, one port, DNS, route) from the campus agent against a switch or device you can already see
network.discovery.viewSee network discovery results: the addresses, models and firmware a sweep found, including discovered addresses in IPAM
network.discovery.manageManage network discovery ranges, credential profiles, runs and the review queue. Approving a range asks you to confirm your identity again. Never given to Ask or a flow
network.manageRefresh from the vendor, map a vendor network to a campus, and from 0.21.0 record subnets and reservations by hand
backup.viewSee backup history
backup.manageSchedule, run, verify and export backups
kb.manageWrite and publish knowledge base articles
docs.viewRead internal documentation and search it
docs.editWrite, update, delete and bind documents
docs.manageSpaces, restriction, and publishing a document to the help page
docs.viewRestrictedRead restricted spaces, on top of docs.view
remote.startStart a remote session on a device
remote.manageConfigure remote access targets
report.viewRun and export reports, the Team view on My time, and read the improvement register and service reviews
report.manageCreate and schedule reports, including at the end of each term; add, edit and move improvements and service reviews, and link records to them

From 0.21.0. The visitor and contractor register needs the Facilities module, which comes with the Campus Operations add-on.

KeyAllows
visitor.viewSee who is on site, today’s visits, visit history and contractors whose Working With Children Check needs attention
visitor.manageSign visitors and contractors in and out at the office, record a sighted WWCC, and add or edit visitor records
visitor.configureRegister settings: host notification for the school and each campus, WWCC reminder notice and recipients. Also needed to change a contractor into a visitor, and to delete a visitor record

visitor.view and visitor.manage are free Participant permissions, so a receptionist who signs people in does not become a paid seat. visitor.configure is a Technical permission. No built-in role other than Owner holds any of the three; an administrator grants them.

Flows are the school’s automation: triggers, conditions and steps across the whole desk.

KeyAllows
flow.viewSee flows, their versions and their runs, the Flows panel on a ticket, repair or person, and the People tab of joiner, mover and leaver runs
flow.buildDraft, edit and duplicate flows, use Describe a flow and the templates, test a draft with a dry run or a backtest, and ask someone else to publish it
flow.publishPublish a version, turn a flow on or off, restore an earlier version, change the owner, and set Flow controls (pause all, two-person publish, protected accounts). Publishing, restoring, turning on and changing the owner ask for step-up
action.manageCreate and manage custom actions, the buttons on records, and choose who may use them. What an action does is a published flow, which needs flow.publish
flow.unattendedTurn on fully automated flows, and the school switch that allows them. A fully automated flow runs its change and privileged steps with nobody asked

Publishing needs more than flow.publish: the publisher must also hold every permission the flow’s steps can use, because a published flow acts on its own within its owner’s access. If the owner later loses one of those permissions, the flow pauses. flow.build and flow.publish are Technical permissions; flow.view is a free Participant permission. Built-in roles that hold workflow.manage hold flow.view, flow.build and flow.publish, and built-in roles that hold ticket.view hold flow.view; grant them to your own roles as you need. flow.publish can never be granted through temporary access.

Connections to other platforms need flow.publish, integration.manage and connector.manage; a flow’s inbound hooks need flow.publish and integration.manage. Both ask for step-up when they change. See external flows and hooks.

KeyAllows
kiosk.viewSee the school’s kiosks: which are online, who is signed in on each and who was. Seeing a person’s kiosk sign-ins from their record also needs client.view

kiosk.view is a free Participant permission, kept apart from feature.manage (which decides where a kiosk sign-in is offered), so the front office can answer “who was on the library iPad at 2pm” without configuring the portal.

KeyAllows
secret.share.createMake one-time links to hand over a password or PIN, and see and revoke your own
secret.share.manageSee and revoke everyone’s one-time links, and set the school’s link policy

A one-time link hands a secret to somebody outside Plugboard, so these keys are kept apart from ticket work. Neither can be given to Ask or a flow.

KeyAllows
label.printPrint labels for repairs and tickets you can open
label.designDesign label templates and choose the defaults

Printing also needs the record’s own view permission and follows campus and department scope. label.design decides what is printed about a person onto a sticker, so it is a separate key and never available to Ask.

PermissionAllows
change.viewSee changes on the service desk (Changes) and in School operations
change.manageCreate and edit changes, link them to tickets, devices and other records, and create a change record from a ticket of type Change
change.approveApprove changes; record why a change cannot wait for a freeze period, which a normal or standard change in a freeze needs before it is approved or started; edit freeze periods and standard changes in Settings, Change rules

These keys govern a change wherever it is reached, so operations.* grants do not reach changes and change.manage never reaches purchases or projects. On a fresh desk only Owner holds them: grant them to the roles that run changes. Letting the requester or owner of a change approve it is a school setting that needs role.manage to change, because whoever holds it can already make anyone an approver. The same setting decides whether a change’s owner may record their own reason to go ahead in a freeze. change.manage makes an account a Business seat; change.view and change.approve are free Participant permissions. See changes.

PermissionAllows
service.viewSee the school’s services, a service’s page and its service levels, including the desk’s targets it falls back on, the services on Home, and Used by on monitors, network devices, devices and printers
service.manageAdd, edit and delete services, link and remove what they depend on, set a service’s fleet, set its service levels and support hours, set or clear a service’s status, mark a service reviewed, and make a service from a monitor

Settings, Roles labels them View services and Manage services. service.view is a free Participant permission. The Technician and Read-only roles hold it, and at start-up it is added to every built-in role that holds ticket.view. service.manage makes an account a Business seat, and only the Owner role holds it to begin with.

Each record a service depends on also needs its own view permission: monitor.view for monitors and provider services, network.view, device.view for devices and printers, software.view for contracts and stock.view for suppliers. A record you cannot open is counted, never named. Choosing or clearing a ticket’s service needs ticket.update. With service.view, naming the services a change affects needs change.manage, naming the service a major incident is about needs ticket.create and ticket.update, and the Service review report and grouping Open problems by service need report.view. Both keys need the Tickets module, and both follow campus scope: somebody limited to some campuses changes only services whose campuses are all inside theirs.

PermissionAllows
operations.viewRead projects, work plans, resources and reservations within the user’s campuses
operations.managePlan work, manage bookings and purchases, request approval, and export purchasing records
operations.approveDecide assigned project, work and purchase approvals; also requires access to the subject. Changes use change.approve
approvals.viewRead ticket approval requests, together with ticket access
approvals.manageRequest and cancel ticket approvals, together with ticket access
approvals.decideDecide ticket approvals assigned to the user, within their ticket and campus access

Calendar publication and team updates also require integration.manage. Synced person onboarding and offboarding planning requires client.view. AV uses the existing network.view and network.manage permissions. Offline stocktake uses device.manage; queued scans are checked again against current permissions.

Approval permission does not let someone decide another person’s assigned step. Changing the business request requires approval of the revised details.

ticket.internal separates the desk’s own notes from working the queue. An internal note is where somebody writes “third time this term, escalate” or “her mother rang, do not put this in writing”, so a school can hand a casual or a student helper the queue without handing them that.

charge.raise and charge.approve separate proposing a charge from making it real. A technician who can propose must not be able to bill a family, and because the person who decides a family pays is the person who can decide they do not, waiving sits with approval rather than with raising.

network.clients.view separates where a device was last seen from both the network estate (network.view) and the device inventory (device.view). Client sightings are location data about a population that is mostly children, so the key is one you grant deliberately: no built-in role except Owner holds it, and it is not a Technician default. Client tracking is off until a school turns it on, and sightings are kept for 7 days by default (90 at most).

network.config.view separates reading a stored network configuration from seeing the estate (network.view). The pane says what is up; a configuration is the firewall rules, the VLAN plan and which wireless network bridges where. Secrets are removed before anything is stored, but the topology that remains is still worth protecting. No built-in role except Owner holds it.

visitor.configure separates switching host notification off from reading or working the register. Whoever may read the on-site list, or sign a visitor in, cannot thereby stop teachers being told their visitor has arrived.

device.wipe.approve makes a wipe happen, which destroys a student’s data and cannot be undone. It is split from device.wipe.request, so the person who asks for a wipe is not, by default, the person who can make it happen.

device.laps.read reads a device’s local administrator password, a credential that grants control of the machine.

Live password, MFA and mailbox permissions can change control of an identity provider account. Re-enabling an account requires both identity.account.manage and identity.account.enable; Full Access grants require both identity.mailbox.delegate and identity.mailbox.fullaccess. identity.tap.issue hands over a working sign-in to somebody else’s account. Grant these keys selectively. The older directory.manage permission does not substitute for the separate live identity.* action permissions.

A role holding * has every permission within its tenant. There is no permission anywhere that crosses a tenant boundary.

API keys carry scopes from this same set. A key cannot exceed them, and on the MCP server a key without a permission does not even see the corresponding tool in tools/list.