Accounts and Members
NexCore accounts are provisioned centrally by an administrator; self-registration is not available. Each account has one role and is granted access to one or more projects, and data is isolated by project.
Creating an Account
Where: System → User Management. Administrators only.
- Click Add User and enter the user's name and sign-in email.
- Select a role: FAE, data collector, R&D engineer, delivery / data owner, and so on. See Roles and Permissions.
- Select the projects the user can access. You can select more than one.
- Click OK. The platform sends an account notification to the sign-in email, and the user can sign in after setting a password.
After signing in, users see only the modules available to their role in the left navigation, and only data in the projects they have been granted.
Bulk-Provisioning Data Collectors
When there are many data collectors, administrators can create their accounts in bulk:
- In User Management, click Bulk Import and download the import template.
- Fill in each collector's name and sign-in email, then upload the file.
- Select a common project and confirm the import.
Data collectors see only the collection tasks assigned to them after signing in.
Managing Accounts
| Action | Description |
|---|---|
| View users | List accounts with their role, granted projects, status, and last sign-in |
| Change role | Change an account's role; takes effect the next time the user refreshes the page |
| Adjust projects | Grant or revoke project access; revoked projects become invisible immediately |
| Reset password | Send a reset link to the sign-in email |
| Deactivate | The account can no longer sign in immediately; it can be reactivated at any time |
What happens to data when an account is deactivated
Collection tasks, data, datasets, models, and deployments created by a deactivated account remain in their projects and are not affected.
Projects and Data Isolation
- Data is isolated by project, and each account sees only data in the projects it has been granted.
- Searches never return data from other projects, and the platform never indicates that such data exists but is inaccessible.
- Models and deployments can be used across projects within the account's access, making them easy to reuse.
Resource Quotas
| Quota | Description | When the limit is reached |
|---|---|---|
| Training compute | The number of training jobs and GPUs that can run at the same time | New jobs are queued |
| Storage | Storage space for data and model artifacts | You're prompted to clean up or expand |
To adjust quotas, contact the platform operations team. See Request Access and Contact.
Audit Logs
Exports, deletions, reviews, permission changes, and similar actions record who performed them and when. Administrators can view them under System → Operation Logs.
Service Regions
NexCore is served from a single domain, with compute and storage nodes deployed by region, and data is stored on the nodes in its region. If data must stay entirely in your own data center, a private deployment is available.

