Memory scopes

Scope only applies to shared memories. A private memory (the ones under Mine) skips this entirely, it's scoped to you, full stop. See Shared and private memories.

When you create a shared memory, you pick one of four scopes. The narrower the scope, the fewer situations a memory is relevant to, and the more specific it can afford to be.

All companies

MSP-level knowledge that holds no matter which customer the AI is working for. Uniportal's own description of this scope: "Uniportal AI may use this on every company." This is where your standing operating procedure lives, not any one account's quirks.

For example: write every resolution note as three short bullets, what was wrong, what you did, what's next. That's true for every customer, so it belongs here, not copied into a memory for each one.

Company

Knowledge specific to one customer: their infrastructure, the industry-specific applications they run, how their processes actually work day to day. Uniportal's description: "Uniportal AI may use this whenever it works on a ticket or task for this company."

For example: Dunder Mifflin Scranton's change window is Saturday 8 PM to midnight, no disruptive changes outside it. Useless context for any other customer, essential every time the AI touches a Dunder Mifflin ticket.

Device

Quirks tied to one specific machine. Uniportal's description: "Uniportal AI may use this whenever it works on this device, or a ticket that involves it."

For example: Kevin's desktop runs an unattended reconciliation job overnight, so nothing should schedule a reboot or patch window before 6 AM. That's a fact about one machine, not about Kevin or about Dunder Mifflin generally.

End user

Knowledge about a specific person. Uniportal's description: "Uniportal AI may use this whenever it works on a ticket or request from this end user."

For example: Creed Bratton doesn't respond to email. Anything urgent for him needs a phone call. Worth knowing the moment his name shows up on a ticket, irrelevant to anyone else's.