--- title: "User Profile and Organization Settings" slug: "profile-and-organization-settings" date: "2026-08-10" tag: "Application" summary: "Two walkthroughs of the panels behind the top-right menu in Agentic OS: the user profile, where each person controls what the AI remembers and how conversations are recorded, and organization settings, where admins brand the tenant, add their own model keys, and issue API credentials." author: "ibl.ai Engineering" linkedin: | Most AI platforms let an administrator decide what the AI remembers about everyone. We think that setting belongs to the person being remembered. Two new walkthroughs of Agentic OS cover the panels behind the top-right menu. The user profile is where an individual decides their own terms: a toggle for whether agents may learn from their conversations, a separate toggle for whether anything learned is used to personalize responses, and a My Memories list they can read, add to, and delete — every saved fact visible in plain language, not buried in an embedding store. Next to it sits Default Private Mode, with three settings. Normal saves conversations to history and links them to the account. Anonymized keeps the content for context but strips the identifying account information. Disabled records nothing at all — every message is a single-turn Q&A, and the agent cannot reference the message before it, even in the same conversation. Any single chat can be flipped into Private Mode from the chat header. Organization settings are the other half: tenant ID, support contacts, light and dark logo uploads, legal links, a footer credit, custom DNS and SMTP, and Advanced CSS — plus the Integrations panel, where the organization brings its own LLM provider keys and issues API credentials with defined permission modes. That last part is the whole architecture in one screen. The models are yours because the keys are yours, the branding is yours because the CSS and the domain are yours, and the deployment runs on your infrastructure — because at ibl.ai you own all the code and the data. #iblai #AgenticAI #EnterpriseAI #AI #DataPrivacy #AIGovernance --- Two walkthroughs are now published for the panels behind the **top-right menu** in Agentic OS — the individual's profile and the organization's settings. They are the two halves of the same surface: one governs a single person, the other governs the whole tenant. ## What does a user control from their own profile?

The user profile panel in Agentic OS.

Every account on the platform has a profile, reached from the avatar in the top right. **Seven tabs** sit in the left rail — Basic, Social, Education, Experience, Memory, Privacy, and Security.

**Basic** holds the identity tied to the account — full name, email, title, a short About bio, and language preference. **Social** connects Facebook, LinkedIn, and X. **Education** splits into three sub-tabs: Education itself (institution, degree, dates, grade), Credentials (verified credentials and badges tied to a unique ID), and Skills — a searchable list where each entry is tagged **Earned**, **Self-Reported**, or **Desired**, so a person can flag what they want to learn, not only what they already know. **Experience** records role, organization, and employment dates, with a Resume sub-tab for uploading a résumé to share with agents and administrators. ## Who decides what the AI remembers about you? The user does. This is the part of the profile worth pausing on, because on most platforms this control does not exist at the individual level at all.

The **Memory** tab is headed *"Manage what the AI remembers about you"* and carries two independent toggles: - **Allow AI to learn from our conversations** — whether agents may capture new memories from chats at all. Turning it off stops new capture; it does not delete what is already saved. - **Use my saved information in responses** — whether saved memories are injected into answers. Turning it off leaves the memories stored but unused. Below them, **My Memories** lists every saved fact in plain language with the date it was created. Auto-captured entries carry a bot icon and an *auto* badge; hand-added ones carry a person icon. The user can add a memory (minimum 10 characters) or delete any entry outright. That list is the point. Memory here is **legible** — a person can read exactly what the system believes about them and remove a line they disagree with, rather than trusting an opaque profile they never see. ## What does Private Mode actually do? The **Privacy** tab sets a **Default Private Mode**, with three mutually exclusive options. The wording below is the platform's own.

Mode	Saved to history	Linked to the account	Context from prior turns
Normal	Yes	Yes	Yes
Anonymized	Yes, for AI context	No — identifying account info stripped	Yes
Disabled	No — nothing is recorded	No	No — every message is a single-turn Q&A

**Disabled** is the strict one, and it is stricter than it first reads: with nothing recorded, an agent cannot reference an earlier message *even inside the same conversation*. The setting is a default, not a lock. Any individual chat can be switched into Private Mode from the chat header, and an agent or the organization can override the default for specific conversations. The **Security** tab rounds out the panel with a password reset by email link and account deletion. The takeaway for a privacy officer: on this platform, memory and recording are governed **per individual and per conversation**, not only by an organization-wide policy switch. ## What can an administrator configure for the whole organization?

Organization settings in Agentic OS.

Flip the header toggle to **Admin** and the same top-right menu opens the organization panel instead — **four sections**: Organization, Management, Integrations, and Advanced.

**Organization** is the tenant's identity: its ID, display name, support email and phone, a Help Center toggle with a custom URL, and separate **light and dark logo uploads** for white-labeling the interface to institutional branding. **Management** covers the people — users, teams, groups, and the roles that define who may do what. ## How do you white-label the platform as your own? Through **Advanced**, which is where an instance stops looking like a vendor's product and starts looking like the institution's.

The panel carries **Legal Links** — your own Privacy Policy and Terms of Use URLs — and a **Footer Credit** field that accepts `{{logo}}`, `{{favicon}}`, and `{{year}}` tokens, so the credit line renders your mark and stays current without an annual edit. **Display Images** holds the imagery shown in the workspace. The rest of Advanced is the platform-wide behavior: chat area width, the authentication interface and **Advanced CSS** for theming, recommendation system prompts, whether users may create their own agents, user-controlled chat privacy, the built-in memory system, public registration, and **DNS and SMTP** configuration so the instance answers on your own domain and sends mail from your own addresses. Custom domain, custom mail, custom CSS, custom legal links, custom footer. Nothing in that list is a co-branding concession — it is the same theming surface we use ourselves. ## Which models and keys does the organization control? Its own. **Integrations** has three tabs, and each one is a place where the organization supplies its own credentials rather than consuming ours.

The APIs tab of the Integrations panel in Agentic OS organization settings, explaining that these are authentication keys generated for external applications and are displayed only once, above a table listing two keys named iblai-cli-nyc and iblai-cli, both with Owner permissions, created June 13th 2026, with no expiry.

**LLMs** stores the organization's model-provider keys. This is the mechanism behind the model-agnostic claim: agents run on whichever providers you hold keys for, and switching provider is a credential change rather than a migration. Keys are stored per organization and served back masked, so the full secret is never redisplayed. **Data Sources** holds credentials for connecting external data services. **APIs** issues authentication keys for external applications to authenticate against the platform, each with a **permission mode** — the two in the screenshot carry *Owner permissions* — and each shown **only once at generation**. Because the deployment runs on the organization's own infrastructure, these settings are the organization's in the literal sense: its branding, its domain, its email, its models, its keys. ## Documentation **User profile** - [Profile: Basic](/docs/os/profile/basic) — name, email, title, bio, and language - [Profile: Memory](/docs/os/profile/memory) — the two personalization toggles and the My Memories list - [Profile: Privacy](/docs/os/profile/privacy) — Default Private Mode, and the per-chat override - [Profile: Education](/docs/os/profile/education) and [Credentials](/docs/os/profile/education-credentials) — degrees, verified credentials, and skills - [Profile: Experience](/docs/os/profile/experience) and [Résumé](/docs/os/profile/experience-resume) - [Profile: Security](/docs/os/profile/security) — password reset and account deletion **Organization settings** - [Organization](/docs/os/organization-settings/organization) — tenant ID, support contacts, Help Center, and logos - [Advanced](/docs/os/organization-settings/advanced) — organization-wide defaults and feature flags - [Integrations: LLMs](/docs/os/organization-settings/integrations-llms) — bring your own model-provider keys - [Integrations: Data Sources](/docs/os/organization-settings/integrations-data-sources) — external data service credentials - [Roles](/docs/os/organization-settings/roles) and [Users](/docs/os/organization-settings/users) — who may do what - [Policies](/docs/os/organization-settings/policies) — organization-level governance settings