Onboarding¶
Welcome aboard 
— this checklist gets you productive at CloudXM. Work top-down; nothing here requires special permission beyond your manager approving the access requests.
Week 1 — Access & accounts¶
| # | Item | Owner | Notes |
|---|---|---|---|
| 1 | CloudXM Google Workspace account | IT admin | Used for e-mail and single sign-on (this wiki, tools) |
| 2 | GitLab account (emcloud group, Developer role) | Tech lead | All code lives here; request access per project |
| 3 | This wiki | Automatic | You are already here via Google SSO  |
| 4 | Linear workspace | Tech lead | Task tracking |
| 5 | Chatwoot (support inbox) | Support lead | Only if you touch client support |
| 6 | Staging environment credentials | Tech lead | Per product, never production first |
Never share credentials
No secrets in chat, no passwords in code, no .env files in git. If you need a credential, ask the owner to put it in the CI secret store (GitLab CI variables) or a password manager.
Week 1 — Reading¶
- This wiki: Products and Architecture
- Operations runbooks — how deploys and incidents work
- Your team's product repo
README.md+AGENTS.md - Implementation playbooks (if you touch client projects)
Week 2 — First tasks¶
- Open your first MR on a real task (see deployment workflow)
- Shadow a support/ops rotation for half a day
- Book a 30-min architecture walkthrough with your tech lead
Tools cheat-sheet¶
| Tool | URL | SSO? |
|---|---|---|
| Wiki (you are here) | wiki.cloudxm.com.br | Google Workspace |
| Code | gitlab.com/emcloud | Google Workspace / personal PAT |
| Tasks | Linear | Google Workspace |
| Company site | cloudxm.com.br | public |
| Support inbox | Chatwoot | per-product admin |
Ask early
The fastest way to get unblocked is asking in the team channel. If something on this page is outdated, fix it — the wiki is a team asset.