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

Find an answer

Browse popular starting points

DocumentationAuras™ and Vibes
Auras™ and Vibes

Job Functions

Understand the role an Aura™ is configured to perform.

Studio / MCP v1Reviewed 2026-10-24
Documentation previewDraft content · Staging instructions · Not approved for production
On this pageThe role of a Job FunctionRole and access are separateChoosing the right Aura™Next steps

The role of a Job Function #

A Job Function defines an Aura™'s working role and responsibilities. It informs how they are curated and the behaviors expected of them.

Role and access are separate #

A Job Function is not a Studio permission role. Calling an Aura™ a technical advisor or an analyst does not grant administrator access, credentials, or application permissions.

Choosing the right Aura™ #

Review the Aura™'s configured role and the knowledge and connections available to them. Use an Aura™ whose responsibilities match your task, and make the intended outcome clear.

Next steps #

Read Auras™ for identity and configuration, and Roles and Permissions for the human and credential access model.

34Five DocumentationPrivacyContent 2b5e203ea2