Roles and RACI Checklist

This page is an optional template. Datature Vi enforces access through organization roles and project roles. It does not run a separate in-product approval workflow for “model release.” Many teams still write down who signs off on labels, who may export weights to production, who owns API keys, and who pays the invoice. Use the tables below as a starting point, then adjust names and RACI letters to match your company.

RACI quick read: Responsible does the work. Accountable approves outcomes (one role per decision). Consulted gives input. Informed gets updates.

Labeling and dataset QA

Who uploads images, edits annotations, and who gives final sign-off is a process choice on top of Vi permissions. Dataset Editors change labels; Viewers read only; Owners control the dataset end to end. See Team settings and Add members.

Training runs and configuration

Training project Owners control workflows, settings, deployments, and deleting the project. Editors create workflows and start runs. Viewers see metrics only. See Team settings.

Model export and production use

Anyone with permission to export can download weights. That usually means people with access to the training project and export flow (see Download a model). Production readiness (security review, latency targets, rollback) remains your Accountable role outside the product. Deployment options are described in How do I deploy my trained model? and Manage models.

Secret keys and billing

Only Owner or Admin can create a secret key. Only Owner changes billing and plan. Admins manage members and resources but not invoices.

Next steps