Accounts and Access
Purpose
Provide one place to request laboratory accounts, compute, remote-network access, and internal tools without transmitting credentials through group chats or public documentation.
Prerequisites
- You are participating in a defined laboratory or course project.
- The required resource, purpose, permission scope, and usage period are known.
- You will request access with a personal account rather than sharing an identity or credential.
Request template
| Resource | Contact | Required information | Guidance | |---|---|---| | GitHub | Wiki Administrator | GitHub username, project, and repository permission | Use a personal GitHub account | | AI API | AI Service Administrator | Project, purpose, model, and usage estimate | See AI API Access and Usage | | Compute | Compute Administrator | GPU, count, duration, and budget source | See Compute Resource Requests and Selection | | Remote access | Network Administrator | Work device, project, target resource, and period | See Remote Access and Private-Network Enrollment | | File storage | Data Storage Administrator | Project, data type, capacity, and members | See Research Data Storage and Archiving | | Internal tools | Service owner | Purpose, required permission, and period | Request through the controlled directory |
Procedure
- Select the resource category and prepare the required information.
- Contact the relevant administrator through the controlled laboratory directory.
- The administrator confirms the project, permission scope, and usage period.
- Receive sensitive configuration through a password manager or one-time secure channel.
- Complete a minimal verification and retain the request record without storing credentials.
Verification
- The personal account can access the approved resource.
- Unapproved projects and services remain inaccessible.
- No real credentials appear in the Wiki, Issues, logs, or repositories.
Troubleshooting
- Permission denied: provide the project and error summary to the relevant administrator, never a password or key.
- Project change or departure: request an access adjustment or revocation.
- Suspected credential exposure: stop using it and contact the administrator for immediate rotation.
Sensitive information
Approved service addresses, hostnames, and IPs may be documented, but never store passwords, private keys, API keys, tokens, Auth IDs, unattended-access passwords, or .env files in the Wiki.