Roll out SynthCrew to your company
A practical administrator path from evaluation to a controlled first engineering task.
1. Decide what the first team will do
Choose a bounded engineering workflow and an owner who can validate its result. Record the input project, expected output, dimensions or constraints, and checks that will establish correctness. Do not start adoption by uploading an entire proprietary project without reviewing data handling.
Read product capabilities, security and privacy. Client processing is remote when enabled. A local project folder does not imply that AI inference or all service records remain local.
2. Choose company capacity, not a per-person subscription
Company pricing is billed per workspace per month. Team includes five named users and a shared $300 provider-cost allowance; Business includes fifteen and $800. An optional $350 pack funds $100 of provider-cost usage. Do not multiply allowance by the number of users.
The pricing calculator estimates the charge; it does not make a purchase. Selecting a plan preserves your intent through sign-in, but checkout still requires explicit action by an authorized workspace administrator. No annual discount, automatic overage or enterprise service commitment is implied.
3. Establish the right account and workspace
- Sign in using the intended Google or GitHub identity. Link another provider only if you control both accounts.
- Confirm that company workspace access is available. Creating an unpaid workspace, when enabled, does not start a paid plan.
- Select the intended workspace before changing members, devices or billing. Do not assume that the last selected workspace is the correct one.
- Keep ordinary engineering membership separate from billing authority. Customer workspace ownership never grants access to the SynthCrew staff support inbox.
If a service is not available, use company enquiries rather than sharing a private Owner installation or account credentials.
4. Invite named users deliberately
Open Team and review the member list and seat limit. An authorized administrator can create a one-use invitation. Copy and share it securely; it expires in one hour. Invitation email is not sent automatically.
Confirm that the intended person accepted the invitation into the intended workspace. Removing membership prevents future authenticated access; it does not erase local engineering files. Establish your own project-sharing, backup and offboarding process.
5. Connect qualified desktops
Follow installation, check the artifact hash and then complete device sign-in. Use Desktops to review connected devices. Revoke a lost or retired device; check the service result before assuming access was removed.
Do not distribute private Owner Codex accounts or a server API key to employees. Customer Client identity and desktop credentials are separate from those private resources.
6. Set spending and engineering boundaries
Use Billing to inspect available allowance and Maximum provider spend per run (USD). The administrator limit is constrained by funded allowance. Included monthly allowance expires at renewal; purchased packs do not expire. No automatic top-up is made.
Choose Plan or Agent and appropriate permissions for the next request. Full Access can allow tools to reach outside a candidate; it is not a sandbox guarantee. Review permissions and tools with the team.
7. Verify the first completed workflow
Use the worked example or a disposable copy of a company project. Check recorded actions, actual candidate files, Preview and explicit Apply. Recompute the result and verify geometry independently. Keep the input and expected result with the review record; an assistant summary is not sufficient evidence.
If a request is interrupted, inspect its recorded outcome and allowance reservation before resending. Follow interrupted-run recovery and support reporting. Never put credentials or a restricted engineering project into an ordinary support request.