Roles and Permissions
NexCore controls access at two levels: which pages are visible, and which actions can be performed. Each account is created by an administrator and assigned one role, which determines visible pages and allowed actions. The data an account can see is determined by its project access; see Accounts and Members.
Roles
| Role | Visible scope | Key actions | Provisioned by |
|---|---|---|---|
| Administrator | All pages | Account provisioning, role and project assignment, compute quotas, auditing | Platform operations team |
| FAE (field application engineer) | All business pages | Create collection tasks, curate data, start pipelines, train, deploy, export | Administrator |
| Data collector | Collection tasks | Claim tasks, bind devices, upload as specified | Administrator (bulk) |
| R&D engineer | All business pages | Upload and configure operators, maintain training templates, export models | Administrator |
| Delivery / data owner | Curation and datasets | Define status criteria, accept dataset versions, set acceptance rules | Administrator |
| Trial user | As granted by the trial policy | Complete the agreed validation in an isolated workspace | Trial provisioning |
Permission Matrix
| Action | Administrator | FAE | R&D engineer | Data collector | Delivery / data owner |
|---|---|---|---|---|---|
| Register devices | ✓ | ✓ | ✓ | — | — |
| Create or edit collection tasks, change target counts | ✓ | ✓ | ✓ | — | — |
| Claim and run collection tasks | — | — | — | ✓ | — |
| Create curation projects, label, and review | ✓ | ✓ | ✓ | — | ✓ |
| Start pipeline processing | ✓ | ✓ | ✓ | Not visible | — |
| Upload operators, configure operator parameters | — | Read-only | ✓ | Not visible | — |
| Export dataset versions | ✓ | ✓ | ✓ | — | ✓ |
| Create training jobs, export checkpoints | ✓ | ✓ | ✓ | — | — |
| Deploy for inference, toggle NexBench | ✓ | ✓ | ✓ | — | — |
| Review bad cases and add them to curation | ✓ | ✓ | ✓ | — | ✓ |
The upload mode can't be changed
The upload mode is set by an authorized role when a task is created and is locked afterward; no role can change it. To use a different mode, create a new task.
Design Principles
| Principle | Description |
|---|---|
| Least privilege | Data collectors can't see models or deployments. |
| Data isolation | Data is isolated by project and isn't visible across projects. Searches never return another project's data, and the platform never indicates that such data exists but is inaccessible. |
| Dedicated permissions | Only R&D engineers can configure operators. Other roles can open the pipeline dialog and see the chain and selected operators, but parameters are read-only, with a message that R&D engineer permission is required. |
| Audit trail | Exports, deletions, confirmations, and similar actions record who performed them and when. |
| Trial isolation | Trial workspaces are separate from production and access is revoked when the trial ends. |
Trial Accounts
The modules available to trial accounts are set by the trial policy. By default, collection, data assets, curation, datasets, training, and deployment are enabled. See Request Access and Contact.

