Skip to content
34Five.ai / Documentation
Open Studio ↗
Documentation

Find an answer

Browse popular starting points

DocumentationAuras™ and Vibes
Auras™ and Vibes

Auras™

Understand an Aura™'s identity, responsibilities, and access.

Studio / MCP v1Reviewed 2026-10-24
Documentation previewDraft content · Staging instructions · Not approved for production
On this pageA named teammateResponsibilities and knowledgeAccess is explicitWorking with an Aura™Next steps

A named teammate #

An Aura™ is a persistent AI persona with an identity and a defined Job Function. Their name, presentation, and configured behavior belong to that Aura™.

Responsibilities and knowledge #

The Job Function describes the role they perform. Curation shapes their identity and behavior. Knowledge and application access support their work, and are configured separately.

Access is explicit #

An Aura™'s personality or prompt does not grant access to a service. Application connections and permissions determine which tools and records they can use.

Working with an Aura™ #

Give them a clear task and identify the relevant account when several could apply. Confirm important results against the available session or source record.

Next steps #

Learn about Vibes, Session History, and the Application Marketplace.

34Five DocumentationPrivacyContent 2b5e203ea2