> 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/equipme/main-menu/basics/my-profile.md).

# My Profile

### **Your Profile in equipme**

Your profile is the place where all your personal information comes together. It decides how you log in, which email address receives updates, and where equipment or other items are sent. When your profile is correct, everything around ordering, approval, and communication works without friction.

***

### **How to open your profile**

You can access your profile from anywhere in equipme.

1. Look at the top-right corner of the screen.
2. Click the small arrow next to your email address.
3. Select **My profile** from the dropdown.

<figure><img src="/files/MxQx3dx7fStqSDjMAGmr" alt=""><figcaption></figcaption></figure>

You will land on a page with several tabs: **Profile**, **Account**, **Permissions**, and **Further information**. Each tab manages a different part of your user data.

***

### **Profile — your basic information**

<figure><img src="/files/8HKTQwSHl8rGwcH2QZSK" alt=""><figcaption></figcaption></figure>

The Profile tab shows your personal details:

* First name
* Last name
* Username (usually your login email)
* Business email (if your organization set one)

If something is incorrect — for example, your name is misspelled — click the small **edit** icon next to “Person” to update it.\
These details are used across the platform, especially in approval flows and order communication.

***

### **Account — your login and invitations**

This section controls how you access equipme.

#### **Password management**

You see your username again and, if you have the rights, an option to reset the password.\
If a password is reset, the user must create a new one the next time they log in.

#### **Login methods**

Depending on what your organization uses, you may log in with:

* **Username / Password**
* **Single Sign-On (SSO)**

If your organization prefers SSO, the admin can set this here before sending an invitation.

#### **Inviting employees**

If you are an administrator, you can invite new users directly from this page by entering their email and choosing the preferred login method.\
This does not apply to regular users.

***

### **Permissions — what you can do in equipme**

The Permissions tab shows you what actions you’re allowed to perform inside equipme.\
Even if you’re an Administrator, some permissions may still come from roles, and role-based permissions can’t be edited here. You’ll see that note at the top of the page.

<figure><img src="/files/Jip45xcmU0BEBbnoLemu" alt=""><figcaption></figcaption></figure>

#### **Record service instances & inventory**

This allows you to manually capture hardware or other items that already exist in your stock.\
You can create active services directly out of inventory without going through the usual approval, ordering, or fulfillment steps.\
Organizations use this when they want to document older devices, retroactively clean up data, or quickly onboard equipment that’s already on the shelf.

#### **Remove service instances & inventory**

With this permission you’re allowed to remove deployed services or delete inventory objects entirely.\
You can skip approval, ordering, and deprovisioning flows to clean things up instantly.\
This is usually only given to people who manage stock or need to fix incorrect entries.

#### **Manage customer settings**

This gives access to portal-level settings for each customer — for example, activating or deactivating order approvals or enabling premium features.\
It requires access to customer management and is often given only to administrators or customer success roles.

#### **Confirm received customer orders**

When a customer places an order, it lands in the provider’s fulfillment pipeline.\
This permission allows you to check and confirm those orders so they can be released for processing.\
Without it, the order stays in a waiting state.

#### **Access to employees for the location manager**

If someone manages a specific location (for example, a branch office or subsidiary), they may need to see employees associated with that location.\
This permission unlocks access to those employees and their services so the manager can keep everything up to date.

***

### **Further information — custom fields**

This tab contains additional information your organization may want to store about you.\
Examples could be:

* Employee ID
* Department
* Location code
* Cost center
* Any other custom attribute

You can add fields using **Add**, or edit existing ones if they’re visible.\
Some companies don’t use this area at all—others use it heavily to support reporting or automatic workflows.


---

# 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/equipme/main-menu/basics/my-profile.md?ask=<question>
```

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.
