User roles
| Action | Everyone | Administrators |
|---|---|---|
| Interact with DevCenter | Users with organization access | ✅ |
| View Marketplace | ✅ | ✅ |
| Build recipes | ✅ | ✅ |
| Create and use access tokens | ✅ | ✅ |
| Deploy recipe and visualization artifacts | ❌ | ✅ |
| View list of repositories | Users with organization access | ✅ |
| View activity log | Users with organization access | ✅ |
| Run recipes and visualizations | Users with organization access | ✅ |
| View recipe results | Users with SCM access | Users with SCM access |
| Commit recipe results | Users with SCM access | Users with SCM access |
| Download data tables | Users with organization access | ✅ |
| View audit logs | ❌ | ✅ |
| View connected connectors and associated technologies | ✅ | ✅ |
| Manage Moddy organization prompts | ❌ | ✅ |
| View and delete user access tokens | ❌ | ✅ |
SCM access
In order to view recipe results or commit recipe results, users will need to have SCM access to the repositories. This restriction applies even for admins in Moderne. Viewing results is gated per repository: if you lack access to a given repository, you'll see the file and change counts but not the underlying diffs. Committing uses your own SCM credentials, so a commit will only succeed for repositories you can push to.
Moddy prompts
Administrators can set the system prompt that steers Moddy for an entire organization, as well as the universal prompt that applies across the tenant. Any user can set their own personal prompt, which overrides the organization and universal prompts for that user.