Member

Member is the default role most people in most orgs carry. It is the end-user surface of Tale — chat with agents, browse the knowledge base, read the conversations and approvals others have routed to you, and leave feedback on replies. Members do not build agents, do not configure providers, do not manage integrations. They use the product the Editors and Developers built for them.

This overview names what a Member can do and points at the per-feature pages. Members typically land on Chat first; the rest of this page is what to read once chat alone is not enough — when you want to know where a citation came from, what an approval card is, or what a project bundles.

What Member covers

The Member surface is intentionally narrow. The four buckets are:

• Chat — pick an agent (or none), send a message, read the reply. The composer surfaces the prompt library, attachments, voice mode, arena mode for side-by-side comparison, and the Canvas pane when a reply produces more than the chat can hold inline.
• Knowledge — browse documents, customers, products, vendors, websites the org has loaded. Read-only for Members; the curating happens on the Editor side.
• Conversations — read the inbox threads assigned to you. Members reply when an agent hands a conversation back; they cannot reassign or close threads other people own.
• Approvals — read the approval cards routed to you. Click Approve, Reject, or Request changes; leave a comment if the rule asks for one.

The org configuration settings — providers, integrations, agents, governance — are hidden for Members; the work surface is the bulk of what is left. The exception is a small personal settings group every role carries: Account, Personalization, and Environment & secrets, the keys and variables injected into the sandboxes you run.

Pages in this section

This section is short — the Member surface is the cross-section of pages that Editors build for and that everyone uses. The deeper reading lives in the per-feature areas.

Chat — the everyday entry point; composer, agents, attachments, citations.

Knowledge overview — the read-only window into what the org has loaded.

Conversations — the unified inbox where customer-channel threads land.

Approval concepts — what an approval card is and what each button does.

Where this fits

Member is the role that consumes what the Editor builds and the Admin governs. The natural first read is Chat — it is where every Member spends most of their time, and most of the other Member surfaces fan out from a chat that wanted to do something more.