> For the complete documentation index, see [llms.txt](https://eirin-ai.gitbook.io/eirin-ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/profile-and-settings.md). # Profile and settings Your agent's settings live on four tabs: Overview, Sources, Reporting and Knowledge base. Replies and the playbook have their own setup flows. Everything you chose while hiring can be changed later. Open the agent's settings by clicking **Settings** on its home card, or click the agent's name in the sidebar. The header shows the agent's name and a **Workspace** button that opens its replies, reports and chat (see [Your workspace](/eirin-ai-docs/working-with-eirin/your-workspace.md)). While the agent doesn't reply anywhere yet, a banner says "{name} can reply too" with a **Set up replies** button. ## The tabs | Tab | What it shows | What you can change | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | **Overview** | Who the agent is, what it reads, where it replies and how it reports: game, sources connected, replies, report schedule, house rules and report guardrails. | Nothing here. Each area is edited elsewhere. | | **Sources** | Everything the agent reads, as cards under **Game store** and **Community and social**, and where it is allowed to reply. | Add or connect a source, open its reply setup, pause reading or replies, or disconnect a community source. | | **Reporting** | The report schedule and where reports go, your studio type, and the option to disable the agent. | **Edit reporting**, **Set studio type**, **Disable {name}**. | | **Knowledge base** | What the agent has been given to read when it replies. | Add, edit or remove knowledge. See [Knowledge base](/eirin-ai-docs/working-with-eirin/knowledge-base.md). | ![The Overview tab](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-c7ab20916b021d669c140c14ee7c928d84862266%2F25_Profile_overview.png?alt=media) ![The Sources tab](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-753bee030325604d23b6a6556f00a5db371bd2fa%2F26_Profile_sources.png?alt=media) ![The Reporting tab](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-0e64c4d22b0cb00219ece63258278dcf5d1c2321%2F29_Profile_reporting.png?alt=media) ## Reporting The **Reporting** section shows the schedule, time zone, where reports are sent and their status ("Sending on schedule"). Switch it **On** or pause it, or click **Edit reporting** to change the schedule. ## Studio type **Studio type** is the biggest lever on how much the agent replies. Choose **Indie**, **Triple-I**, **AA** or **AAA**. Each channel's Reply config then shows the reply rate this gives, for example "replies to about 40% of the flexible layer". Until you set it, the agent's reply rate can't be shown. ## Replies and guardrails Reply settings now live in [reply setup](/eirin-ai-docs/getting-started/set-up-auto-replies.md), one channel at a time: guardrails, tone, how much it replies, situations, policies and reply timing. The studio-wide **house rules** and the **report guardrails** (topics left out of reports) are edited in the agent's edit flow. On the home page, click **Edit** on the agent's spotlight card, then go to the **Playbook** step. Add a rule with **+ Add** and remove one with **×**. Changes save as you go, as the **Saved** label at the top shows. ![The Playbook step of the edit flow](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-9a7861ae25e9b6d485a534b72e56e49eb6117900%2F57_Edit_playbook.png?alt=media) ## Disable an agent At the bottom of the **Reporting** tab, click **Disable {name}**. The agent stops reading, replying and sending reports on every channel, and its work email is freed for another agent. Its playbooks, settings and history are kept, and you can enable it again at any time. ## Related pages * [Set up Eirin](/eirin-ai-docs/getting-started/set-up-eirin.md): where these settings were first chosen * [Set up auto-replies](/eirin-ai-docs/getting-started/set-up-auto-replies.md) * [Your workspace](/eirin-ai-docs/working-with-eirin/your-workspace.md): replies, reports and chat --- # 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://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/profile-and-settings.md?ask=&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.