Titled memos & granular Agent API Keys
Two updates giving your agents sharper, safer access: titled Network memos and fine-grained Agent API Key permissions.
Two updates this week, both about giving your agents sharper, safer access to your business.
Titled Network memos
Memos on a contact now carry a title, in the app and across the REST API. As you point more agents at NOAN, they write to contact memos automatically, and that history can pile up fast. A title on each memo acts as an orchestration layer for a contact's context: you (and any agent reading the record) can see at a glance what each memo covers instead of scrolling through raw text. Titles can be set manually or generated by the NOAN assistant, and they're exposed on the API so anything you build can read and write them too.
Granular, switch-based Agent API Keys
Agent API Keys now support fine-grained, on/off permissions so you can hand an agent exactly the access it needs, and nothing more:
- Read and Write toggles per feature - Facts, Notes, Tasks, Assets, Contacts.
- Facts scoped by stack: grant an agent all facts in a stack, or drill in and toggle individual facts, for read and for write.
- A separate "Allow agent to create new facts" switch, independent of read/write on existing facts.
- Manage, edit, or revoke existing keys from Settings > API.
The result: every agent you build on NOAN can be given least-privilege access to your fact base, so you stay in control of exactly what each one can see and change.

.png)
.png)

.png)
.png)
.png)
.png)
.png)

.png)
.png)
.png)
.png)
.png)

.png)
.png)

.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)



.avif)

.avif)

.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)

.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)