What Does an Admin Need to Set Up Before the Team Can Use Dave by voolama?

All four steps require the Admin role. Only the Admin role can access Admin, then API Management, then Providers and Admin, then Settings, then Users and Roles. Sourced from the getting-started help documentation, DEV v0.11.0, confirmed against content_orchestrator main at commit ddb945f, 2026-08-30.

1. Step 1: Configure at least one AI provider. Navigate to Admin, then API Management, then Providers. Click Create Provider. Enter a name (for example, "OpenAI Production"), select the provider type, enter the base URI, and provide the API key. Click Save. Seven provider types are available: OpenAI, Anthropic, Azure OpenAI, Google, OpenAI-compatible, local (Ollama), and custom. You bring your own API keys: Dave by voolama never proxies or marks up AI usage. Credentials are stored in a per-tenant vault encrypted with AES-256-GCM authenticated encryption and are never returned through the API once stored. Verify: after saving, the provider row appears in the Providers list with a green status indicator. No vendor trust required. See Add an AI Provider for the full provider setup path.

   Provider type	What you need
   OpenAI	API key from platform.openai.com
   Anthropic	API key from console.anthropic.com
   Azure OpenAI	Endpoint URL and API key from Azure portal
   Google	API key from Google AI Studio or Vertex AI
   OpenAI-compatible	Base URI and API key for any OpenAI-compatible endpoint
   Local (Ollama)	Ollama base URI (model runs on your own machine, not on Dave by voolama infrastructure)
   Custom	Base URI and authentication as defined by the provider

2. Step 2: Create user accounts and assign roles. Navigate to Admin, then Settings, then Users and Roles. Click Create User for each team member. Assign each user the role or roles they need. Dave by voolama has six default roles: Admin, Create, Curate, Use, Reporting, and Financial. Roles are editable. A user can hold multiple roles simultaneously.

   Role	What the user can do	Sidebar items they see
   Admin	Full tenant control: users, settings, providers, feature flags	All items including Admin section
   Create	Build and manage AI agents and agent versions	Dashboard, Agents
   Curate	Design workflows in the visual editor	Dashboard, Agents (read), Workflows
   Use	Launch instances and complete tasks	Dashboard, Calendar, Instances, Tasks
   Reporting	View reports and audit logs	Dashboard, Reports
   Financial	Billing and plan management	Dashboard, Admin Billing section

   The getting-started help documentation states: "If you do not have a role that grants access to a feature, the corresponding sidebar link does not appear and direct URL access returns a 403 error." Verify: log in with a newly created Use-role account. Confirm the Agents and Workflows sidebar links are absent. Confirm the Instances and Tasks links are present. No vendor trust required.

   Optionally, configure MFA enforcement before team members log in for the first time. NIST SP 800-63B section 6.1.2 requires multi-factor authentication for Authenticator Assurance Level 2 (AAL2). Dave by voolama supports eight MFA provider types. See How Do I Enforce Multi-Factor Authentication for My Team in Dave by voolama? for the full MFA setup guide.

3. Step 3: Run the end-to-end verification walkthrough. Before handing the tenant to the team, verify the full pipeline works. The getting-started help documentation documents a 9-step quick-start walkthrough. The condensed version:

   1. Navigate to Agents. Click Create Agent. Name it "Test Agent". Add a version with a system prompt (for example, "Summarize the provided text in three bullet points"), a model (for example, gpt-4o), and a temperature of 0.7. Save.
   2. Navigate to Workflows. Click Create Workflow. Open the Workflow Editor. Drag a Start node, a User Interaction node, an Agent Interaction node (select "Test Agent"), a Human Review node, and an End node onto the canvas. Connect them in sequence. Save. See Build Your First Workflow for the editor walkthrough.
   3. Navigate to Instances. Click Create Instance. Select the workflow and its latest version. Launch. See Launch an Instance.
   4. Navigate to Tasks. Open the User Interaction task. Enter sample text. Submit.
   5. Wait for the Agent Interaction node to complete. A Human Review task appears.
   6. Open the Human Review task. Click Approve.
   7. Navigate to Instances. Confirm the instance status is completed.

   Verify: all seven sub-steps are independently observable in the UI. If any step fails, the failure mode tells you exactly which dependency is missing. A failure at step 4 means the User Interaction node is misconfigured. A failure at step 5 means the provider or agent configuration is incorrect. No vendor trust required.

4. Step 4: Enable feature flags your team needs. Navigate to Admin, then Settings, then Feature Flags. The getting-started help documentation names three examples: advanced_nodes (additional node types), split_join (parallel branch execution), and pdf_export (export instance outputs as PDF). All flags are off by default. Enable only the flags your team's workflows actually require. Verify: after enabling a flag, navigate to the Workflow Editor and confirm the corresponding node type or option appears in the left palette. No vendor trust required.

This checklist covers the four Admin first-day setup steps in Dave by voolama (hellodave.ai) at DEV v0.11.0. Three things it does not cover:

• MCP key setup. If your team uses AI assistants (Claude Code, Claude Desktop, VS Code, JetBrains) connected to Dave by voolama over MCP, each user needs a personal MCP key. MCP key setup is covered at Connect an AI Assistant over MCP. Dave by voolama provides 34 MCP tools across four capability presets. MCP keys are per-user and are configured separately from the provider and user account setup in this checklist.
• SSO/OIDC configuration. If your organisation uses single sign-on, Dave by voolama supports five SSO/OIDC providers: Google, Microsoft, GitHub, Okta, and custom OIDC. SSO is configured at Admin, then Settings, then Access, then OAuth. SSO configuration is a separate task from the user account creation in step 2 of this checklist and is not covered here.
• Ongoing tenant administration. This checklist covers day-one setup only. Ongoing tasks such as rotating provider API keys, managing agent versions, adjusting retention policies, and reviewing the audit log are covered in the feature-area documentation for each section.