GitHub and Wiki.js access support code contribution, pull requests, reviews, and documentation updates.
Accounts & Access explains the systems, accounts, and permissions a new developer may need when joining the UtopiaSystem team.
Use this page as an onboarding checklist so new team members know what access to request, who may need to approve it, and what each account is used for.
This page separates platform access, local development access, and UtopiaSystem application access so each request can be reviewed clearly.
GitHub and Wiki.js access support code contribution, pull requests, reviews, and documentation updates.
Supabase, Google Cloud, and secure local configuration support auth, database, OAuth, and debugging work.
Vercel and DigitalOcean access support frontend and backend deployment checks, logs, and environment configuration.
UtopiaSystem permissions control what developers can test inside Launcher, Personal, Work, HR, Finance, and OE spaces.
This page explains the accounts, systems, and access permissions a new developer may need when joining the UtopiaSystem team.
New developers should understand:
UtopiaSystem development involves several platforms. Access should be granted based on role and responsibility.
| Platform | Purpose |
|---|---|
| GitHub | Source code, pull requests, deployment workflows |
| Supabase | Authentication, database, storage, policies, logs |
| Vercel | Frontend deployments and environment variables |
| DigitalOcean | Backend deployment and container services |
| Google Cloud | Google OAuth and related Google services |
| Wiki.js | Internal documentation |
| Communication tools | Team updates, questions, and release coordination |
Not every developer needs full admin access to every platform.
Access should be role-based, individual, limited, and reviewed when responsibilities change.
The main platform accounts are listed below with their typical use cases and access levels.
GitHub is required for developers who work on the codebase.
Supabase access may be needed for authentication, data inspection, policies, storage, logs, and Edge Functions.
Production Supabase access should be restricted because mistakes can affect real users and live data.
Vercel access supports frontend deployment logs, deployment history, custom domains, environment variables, rebuilds, and frontend deployment debugging.
Environment variable access should be limited because it may expose sensitive configuration.
DigitalOcean is used for backend deployment infrastructure, especially backend services such as Finance Backend and OE Backend.
Google Cloud is mainly connected to Google OAuth and Google-related integrations.
Wiki.js access is used for reading system documentation, updating onboarding pages, maintaining module documentation, adding deployment notes, and recording troubleshooting steps.
New developers should usually have Reader access first. Documentation owners should have Editor access.
Use the tables below to choose the lowest useful access level for each platform.
| Platform | Access Level | Suitable For |
|---|---|---|
| GitHub | Read | Viewing code and documentation |
| GitHub | Write | Creating branches and pull requests |
| GitHub | Maintain | Managing repository settings and workflows |
| GitHub | Admin | Full repository administration |
| Supabase | Viewer | Read-only inspection |
| Supabase | Developer | Development and debugging |
| Supabase | Admin / Owner | Production-level configuration and billing |
| Vercel | Viewer | Read deployment status and logs |
| Vercel | Developer | Trigger deployments and inspect projects |
| Vercel | Admin | Manage environment variables, domains, and project settings |
| DigitalOcean | Read-only / Viewer | Checking service status and logs |
| DigitalOcean | Developer | Deploying or restarting services |
| DigitalOcean | Admin | Managing infrastructure, billing, and sensitive settings |
| Google Cloud | Viewer | Inspecting configuration |
| Google Cloud | Editor | Updating OAuth and service settings |
| Google Cloud | Owner | Full project control |
| Wiki.js | Reader | Reading documentation |
| Wiki.js | Editor | Writing and updating pages |
| Wiki.js | Admin | Managing Wiki.js settings and permissions |
Most developers usually need GitHub Write access. Admin access should only be given to team leads or maintainers.
Developers also need local access to project configuration, examples, and testing details.
.env example file.Sensitive values should not be copied into public documents. If credentials are required, share them through the approved secure channel.
Developers may also need UtopiaSystem app access for testing workflows inside the product.
| Access Area | Purpose |
|---|---|
| Launcher | App entry and workspace navigation testing |
| Personal Space | Self-service employee testing |
| Work Space | Approval and team workflow testing |
| HR Space | HR module testing |
| Finance Space | Finance workflow testing |
| OE Space | Operation efficiency testing |
| Sales Space | Sales workspace and Encik Beku access testing |
| Developer Tools | Access Manager, User Access, audit, roster |
Access inside UtopiaSystem is controlled by user permissions, feature access, and data scopes. Sales access uses sales.app.access for the app and workspace-specific grants such as sales.encik-beku.view.
A developer may have platform access, such as GitHub or Vercel, but still not have application access inside UtopiaSystem. These are separate access layers.
Use this checklist when onboarding a new developer.
| Access | Required? | Notes |
|---|---|---|
| GitHub repository | Yes | Needed for code contribution |
| Wiki.js | Yes | Needed for documentation and onboarding |
| Supabase | Depends | Needed for database/auth debugging |
| Vercel | Depends | Needed for frontend deployment debugging |
| DigitalOcean | Depends | Needed for backend deployment debugging |
| Google Cloud | Depends | Needed for OAuth or Google service work |
| UtopiaSystem test account | Yes | Needed for app testing |
| Developer tools in Work Space | Depends | Needed for access-control work |
| Production data access | Restricted | Only when approved |
Access requests should include enough context for the team lead or platform owner to approve the right level.
Name: New Developer
Email: developer@company.com
Platform: GitHub
Access requested: Write
Reason: Need to work on UtopiaSystem frontend tasks and submit pull requests.
Approved by: Team LeadAccess should be removed when it is no longer required or when a person leaves the team.
Developers must protect secrets, credentials, production data, and automation tokens.
Do not make production changes, share secrets, or grant admin access without approval.
.env files.
Do not expose service role keys.
Do not copy production secrets into documentation.
Do not use personal tokens for shared automation.
Do not give admin access unless required.
Do not make production changes without approval.
Report leaked secrets immediately.
Rotate secrets if exposure is suspected.
Use MFA where possible.
Accounts and access are required for developers to work safely across UtopiaSystem.
Access should always be role-based, limited, reviewed, and removed when no longer needed.