> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/suppliers/suppliers/administration.md).

# Administration

With a complete profile, you give buyers the information they need to do business with your company. This includes information about your company, the goods and services you provide, your locations and where you provide service, your certifications, and contacts. With complete information, you will be more visible to buyers in Fairmarkit, reduce the emails on non-relevant opportunities, and access more legitimate sales opportunities.

**Admin Access**: To access the Administration settings, you will need to be assigned to the *Admin* role for your organization. To request Admin access, from the top menu, click your name and then select *Request admin role.*

**Admin Role Benefits:** As an Admin, you’ll have full visibility into all RFQs your company is invited to—even if your individual email wasn’t directly included. You’ll also have the ability to reassign RFQs to the appropriate representative if the wrong contact was invited.

[Company Info](/suppliers/suppliers/administration/company-info.md)

[Products & Services ](/suppliers/suppliers/administration/products-and-services.md)

[Locations](/suppliers/suppliers/administration/locations.md)&#x20;

[Certifications](/suppliers/suppliers/administration/certifications.md)&#x20;

[Contacts ](/suppliers/suppliers/administration/contacts.md)

[Catalogs ](/suppliers/suppliers/administration/catalogs.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fairmarkit.com/suppliers/suppliers/administration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
