Changelog

Member profiles open a member's work to owners and admins

A member's profile in your workspace is now a set of tabs. Usage comes first, as before, and it is all most members see. Owners and admins also get Chats, Resources, Files and Integrations, each listing what that member has. You stay signed in as yourself the whole time.

How it works

  • Seeing a member's work. The permission lets you see a member's chats, specialists, skills, files, workflows, deliverables, databases, data stores and integrations. You can read a conversation, even one still running, but not send in it, and opening it doesn't mark it read for them. You can browse and download their tables and files, and looking changes nothing and doesn't count as use.
  • Apps. A member's app opens and runs for you, as it does for anyone a specialist is shared with, since opening an app runs it.
  • It only adds. The permission never takes away access you already have. Owners and admins can still edit and run any member's workflow, app or deliverable, and a share or another permission you hold keeps working as before.
  • Integrations. Through the permission you see a connected account's name, status and scopes, never its keys, and you can't sync or use it unless it is shared with you.
  • Who can. Owners and admins, or anyone on a team you give "View any member's chats, resources, files and integrations". It covers every member of your workspace, owners included.

Also shipped

  • A member's specialist opened from their profile shows their conversations with it, building on admins viewing any specialist.
  • A live browser in a member's conversation stays with them: someone reading the conversation sees its steps, never the browser itself.

Your first specialist starts here.

Give it one job. Build the workflows, apps, and skills to get it done.