> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/administrative-functions/manage-organizational-structure/employee-management/permissions.md).
# Permissions
Roles set the baseline. Sometimes, though, you need to fine-tune what a single person can do. That’s what the **Permissions** tab is for.
**Path:** **My Company → Employees → (open employee) → Permissions**\
\&#xNAN;*Note at the top of the page:* permissions that come **from assigned roles** can’t be edited here. You can only add or restrict what isn’t already locked by a role.
**1) Self service**\
Let this person request services on their own in the marketplace. Orders still follow your approval rules—this doesn’t bypass approvals.\
\&#xNAN;*Use when:* you want normal employees to “shop” their work essentials.\
\&#xNAN;*Turn off when:* requests must always be created by managers or IT.
**2) Show prices and costs**\
Shows unit prices in the marketplace and costs in self-service/controlling views (only applies to self-service views).\
\&#xNAN;*Use when:* you want transparency (e.g., cost-aware ordering or chargeback culture).\
\&#xNAN;*Turn off when:* you prefer employees to pick by policy, not by price.
**3) Access to the entire marketplace**\
Lets the person request **all** services offered - also those not explicitly enabled for self-service.\
\&#xNAN;*Use when:* power users or IT staff should see/request everything.\
\&#xNAN;*Caution:* keep approvals in place; this is broad visibility.
**4) Record service instances & inventory**\
Allows creating active service instances **without** running through approval, ordering, or fulfillment (e.g., retroactive entry from existing stock).\
\&#xNAN;*Use when:* onboarding historical assets, warehouse/asset ops, data clean-ups.\
\&#xNAN;*Caution:* it skips process steps - treat as an operator power tool.
**5) Remove service instances & inventory**\
Allows removing inventory objects and active service instances **without** approval or deprovisioning flows.\
\&#xNAN;*Use when:* senior asset managers need to correct data quickly.\
\&#xNAN;*Caution:* high-impact. Removing outside the standard offboarding can affect billing, compliance, and audit history. Keep this tight.
**6) Access to employees for the location manager**\
Gives access needed to manage employees and their services for a location.\
\&#xNAN;*Use when:* someone acts as **location manager** and must support “their” site without full admin rights.
#### Saving and reviewing
After changing any toggle, click **Save**. Revisit these settings when someone changes team, role, or responsibilities.
At the bottom you’ll see **Roles** assigned to this person (e.g., *User*, *Team Manager*). Those links take you straight to the role configuration:\
**Settings → Roles & rights**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://hub.equipme.io/classes/administrative-functions/manage-organizational-structure/employee-management/permissions.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.