What is a project?
A project is the unit that separates work environments in wiiiv.
Within a single project, knowledge (documents), policies (allowed scope), models (LLM settings), and connections (external APIs and folders) are configured independently. Every conversation created in that project follows these settings.
For example, you can connect brand guidelines and ad asset folders to a "Marketing" project, and API specifications and code repositories to a "Development" project. Each team's conversations only reference their own project's knowledge and are governed only by their own project's policies, so work never gets mixed.
Project list
Select Projects from the ☰ menu to view all projects. Use the + New Project button in the upper right to create a new project.
Default — New conversations are created in this project by default.
Active — The currently selected project.
OWNER — The project owner who can manage policies and members.
Project detail — Overview
Click a project card to open the detail view. There are 7 tabs at the top, with Overview being the first.
Policy tab — Usage policies
The project owner defines the rules for this project. You can set usage limits, allowed features, and external API access scope.
Usage Limits
Executable Features
Manage the executors and plugins available in this project with toggles. Disabled features are blocked from running in this project's conversations and workflows.
External API access control
Restrict the scope when workflows call external APIs. If left empty, all domains and methods are allowed.
API Keys tab
Manage API keys for external systems to access this project. Generated keys inherit this project's policy.
Each key inherits the project's policy and permissions.
Store keys securely; they cannot be retrieved after creation.
| Key Prefix | Label | Created | Actions |
|---|---|---|---|
| No API keys | |||
LLM Settings tab
Configure the LLM provider, API key, and model to use in this project.
Provider: OPENAI | Governor Model: gpt-5.4-mini
Personal key vs. project key — By default, each member's personal API key is used. If you register a project key and enable the "Share" option, members can use this project's LLM without their own key.
Model selection — Specify the Governor (judgment), Generator (generation), and Embedding (vectorization) models separately. Model selection is independent of the API key source.
Knowledge Base tab
Manage project-specific knowledge. Separate from global knowledge, these documents are referenced only in this project's conversations and workflows.
Inlet Channels tab
Two-way channels that allow conversations to be started from outside wiiiv. Only the project owner can manage these.
SLACK — A Slack bot receives messages and forwards them to a wiiiv session. Results are sent back to Slack.
CRON — Runs automated conversations on a set schedule. Used for periodic reports, monitoring, and more.
Status — Running (active) / Stopped (inactive). Control with Start/Stop.
Permissions — Permission level (VIEWER, etc.), Allowed Methods (GET, etc.), and Max Turns limits are applied.
Audit Log tab
View all judgment, execution, and approval/rejection records from this project.
Every action in wiiiv is recorded. You can transparently track who requested what, when, how the AI judged, and what it executed.
Permission structure
Project permissions are divided into three tiers. Admin manages the system, OWNER (team lead) designs the project, and Members work within it.
| Feature | Admin | OWNER | Member |
|---|---|---|---|
| Create Project | ✓ | ✓ | — |
| Policy Settings | ✓ | ✓ | — |
| Invite Members | ✓ | ✓ | — |
| Chat | ✓ | ✓ | ✓ |
| Run Workflows | ✓ | ✓ | ✓ |
| Manage Inlets | ✓ | ✓ | — |