Skip to content
For Self-Managed AI Platform users running v11.1, see the self-managed platform documentation
NextGen UI documentation > Registry > Memory spaces

Memory spaces

Premium

DataRobot's Agentic AI capabilities are a premium feature; contact your DataRobot representative for enablement information.

The Memory spaces page in Registry is a centralized place to view and manage memory spaces for agentic applications. A memory space is an isolation boundary for chat sessions, events, and long-term semantic memories. From Registry, you can see every memory space you created, own, or that another user shared with you.

Access the page from Registry > Memory in the left sidebar.

Column Description
Label The display name assigned to the memory space (for example, Vadym's personal memory or Space 0e885f27).
Memory Space ID The unique identifier (UUID) for the memory space. Click the copy icon to copy the ID to your clipboard for use in API calls.
LLM model name The LLM used for semantic memory extraction in this space, if one is configured (for example, bedrock/anthropic.claude-sonnet-4-6). Displays No model configured when no model is set.
Created When the memory space was created, shown as a relative time.

Use the filter tabs and search bar to narrow the list of memory spaces:

  • All: Shows every memory space you can access, whether you own it or it was shared with you.
  • Owned: Shows only memory spaces you created.
  • Shared with me: Shows only memory spaces another user shared with you.

Enter text in the search field to filter by Label or Memory Space ID. The table updates as you type.

Create a memory space

Availability information

Access to the agentic memory API is off by default. Contact your DataRobot representative or administrator for information on enabling this feature.

Memory spaces are created programmatically through the REST API or Python API client. See Create a memory space in the agentic memory service documentation.

When you create a space through the API, you can set a description (shown as the Label on the memory spaces page) and an optional llm_model_name (shown in the LLM model name column). Memory spaces without an LLM model name appear as No model configured in the UI.

Share a memory space

The sharing capability allows appropriate user roles to grant permissions on a memory space. This is useful when multiple users or teams need read or write access to the same agentic memory. For example, a shared support assistant whose facts are maintained by one team and consumed by another.

Access levels and sharing

You can only share up to your own access level (a Consumer cannot grant an Editor role, for example) and you cannot downgrade the access of a collaborator with a higher access level than your own.

To share a memory space, open the Actions menu at the end of the row and select Share ().

This opens the Share dialog, which lists each collaborator and their role.

Sharing roles

When you share a memory space, assign one of the following roles:

Role Access
Consumer Read-only. The user can see the memory space in Registry and read existing sessions, events, and semantic memories through the UI and API. They cannot insert new facts, post events, or modify the memory space.
Editor Read and write. The user can read the memory space and ingest memories, post events, and create sessions within it. They cannot delete the memory space or change sharing settings unless they also hold Owner.
Owner Full control. The user can read, write, delete, and re-share the memory space, including granting any sharing role to others. The creator of a memory space is automatically assigned Owner. Existing owners can grant Owner to another collaborator through the Share dialog.
  1. Enter a username in the Share with field.
  2. Choose a role from the dropdown (Consumer, Editor, or Owner).
  3. (Optional) Select Send notification and Add note to include details in the email notification.
  4. Click Share.
  1. Select the Groups or Organizations tab in the Share dialog.
  2. Enter the group or organization name in the Share with field.
  3. Select a role for permissions.
  4. Click Share. The memory space is shared with every member of the designated group or organization.

Revoke access

To remove a user's access to a memory space:

  1. Open the Share dialog for the memory space.
  2. At the end of the row for the user, group, or organization you want to revoke, click the revoke icon ().

Access is removed immediately. The revoked user loses all permissions on that memory space and will no longer see it under Shared with me or be able to call memory service APIs for it.

To change an existing collaborator's role without revoking access, select a new role from the Role column dropdown.

Permissions and access

Memory space access is controlled at two levels:

  1. Agentic memory API access — An administrator enables Enable Access to Agentic Memory API on your user profile. Without it, you cannot open the Memory spaces page or call the memory API. See Enable access to the agentic memory API.

  2. Per-space sharing — The Owner of a memory space (or a user with sufficient share permissions) grants Consumer, Editor, or Owner access to specific users, groups, or organizations through the Share dialog. All three roles appear in the role dropdown. Editor and Owner can ingest memories and post events; Consumer is read-only.

With API access enabled, you see memory spaces you own or that were shared with you—not every memory space in the organization. To ingest into a shared space, you need Editor or Owner on that space, not Consumer only.

Sharing is managed in the Share dialog on each memory space. See Manage sharing in Registry.

See also