User Roles & Permissions¶
Understanding VDC's role-based access control system is essential for getting the right permissions to accomplish your goals. This guide covers all access levels, how to request them, and what each role can do.
VDC Access Overview¶
VDC uses a layered permission system based on AGS groups:
- System Access - Basic access to VDC (VDC-USERS AGS group)
- Project Access - Contributor (write) permissions within specific projects (Project AGS groups)
Step 1: Get VDC system access¶
VDC-USERS AGS Group (Required for everyone)¶
What it provides: Read access to all VDC projects - browse, search, and download ingredients across the entire platform.
How to get access:
- Request membership: VDC-USERS AGS Group
- Wait for approval: Typically 1 business days
- Verify access: Visit VDC Portal - you should see the projects dashboard and continue navigate based on your needs
Important
This is required for all VDC users. Without VDC-USERS membership, you cannot access the VDC system at all.
Step 2: Get project-level access¶
Each VDC project has three AGS groups that control different permission levels:
Project AGS Groups Structure¶
- [ProjectName]-Admins - Project administrators with full management permissions
- [ProjectName]-PowerUsers - Power users with ingredient management and workflow creation
- [ProjectName]-Users - Standard project users who can submit releases and run workflows
How to Request Project Access¶
- Identify the project you need access to
- Contact the project administrator - they manage group membership
- Request appropriate level - usually Project Users is sufficient for most work
- Wait for approval - project admin will add you to the relevant AGS group
Tip
If you don't know who the project administrator is:
- Submit HSD ticket: Create HSD ticket with component "VDC" requesting project access information
- Contact VDC support: Reach out to the VDC support team for assistance in connecting with the right project administrator
Role permissions matrix¶
Action | VDC User | Project User | Project Power User | Project Admin |
---|---|---|---|---|
View Project | ✅ | ✅ | ✅ | ✅ |
View Ingredient | ✅ | ✅ | ✅ | ✅ |
View Ingredient Release | ✅ | ✅ | ✅ | ✅ |
Download Ingredient Release Package | ✅ | ✅ | ✅ | ✅ |
Create / Edit Ingredient | ❌ | ❌ | ✅ | ✅ |
Submit Ingredient Release | ❌ | ✅ | ✅ | ✅ |
Delete Ingredient | ❌ | ❌ | ❌ | ✅ |
Delete Ingredient Release | ❌ | ❌ | ❌ | ✅ |
View Workflow | ✅ | ✅ | ✅ | ✅ |
Create / Edit Workflow | ❌ | ❌ | ✅ | ✅ |
Run Workflow | ❌ | ✅ | ✅ | ✅ |
Delete Workflow / Workflow Run | ❌ | ❌ | ❌ | ✅ |
Role descriptions¶
VDC User (VDC-USERS AGS Group)¶
Who: All VDC users must have this level
Permissions:
- Browse all projects and feeds
- Search ingredients globally
- View ingredient details and releases
- View workflows (but cannot create, edit, or run them)
- Download release packages
- Access VDC web portal and CLI
Cannot do:
- Create or edit ingredients
- Submit releases
- Run workflows
Project User ([ProjectName]-Users AGS Group)¶
Who: Team members who need to work within a specific project
Permissions:
- All VDC User permissions, plus:
- Submit ingredient releases
- Run workflows within the project
Cannot do:
- Create or edit ingredients
- Create or manage workflows
- Manage project settings or user access
Project power users ([ProjectName]-PowerUsers AGS Group)¶
Who: Advanced team members who need ingredient and workflow management capabilities Permissions:
- All Project User permissions, plus:
- Create and edit ingredients
- Create and edit workflows
Cannot do:
- Delete ingredients or releases
- Delete workflows or workflow runs
- Manage project settings or user access
Project Admin ([ProjectName]-Admins AGS Group)¶
Who: Project leaders and technical leads
Permissions:
- All Project Power User permissions, plus:
- Delete ingredients and releases
- Delete workflows and workflow runs
- Manage project settings
- Add/remove users from project AGS groups
Responsibilities:
- Manage project AGS group membership
- Oversee project organization and structure
- Handle project-level access requests
Access request process¶
For New Projects¶
If you need to create a new project, see: Creating Your First Project
For existing projects¶
Follow How to Request Project Access
Troubleshooting access issues¶
"I can't access VDC at all"¶
Solution: Request VDC-USERS AGS group membership
"I can browse but can't create ingredients"¶
Issue: You need to to have project power users access Solution: Request membership in [ProjectName]-PowerUsers AGS group from project admin
"I can't run workflows"¶
Issue: Need Project User access
Solution: Request membership in [ProjectName]-Users AGS group from project admin
"I can't create workflows"¶
Issue: Need Project Admin access Solution: Request membership in [ProjectName]-Admins AGS group from project admin
Next steps¶
Got Access?¶
- Browse VDC: Start exploring projects and ingredients
- Choose Your Path: Quick start guides for role-specific next steps
Need a Project?¶
- Create New Project: Creating Your First Project
Need Definitions?¶
- Terminology: VDC glossary
Still having issues
- Contact VDC support team for technical assistance
- Use VDC user channel for support