Skip to main content

Getting Started

This guide takes a new tenant from sign-up to first production-ready workflow.

Before You Begin​

  • You have tenant admin access.
  • You know your initial team members and their roles.
  • You have one pilot project in mind.

Step 1: Create the Tenant Workspace​

  1. Sign in to the Chyper console.
  2. Confirm your tenant name and primary workspace.
  3. Set your preferred timezone and notification defaults.
  4. Save tenant settings.

Outcome: Your tenant boundary and default workspace are active.

Step 2: Invite Team Members and Assign Roles​

  1. Open Settings -> Team.
  2. Invite users by email.
  3. Assign roles based on responsibility:
    • Owner/Admin: platform governance.
    • Developer/Manager: project delivery.
    • Viewer: read-only stakeholders.
  4. Confirm each user can access only expected areas.

Outcome: Role-based access is in place.

Step 3: Create Your First Project​

  1. Open Projects -> New Project.
  2. Enter project name, goal, and scope.
  3. Add an initial requirement set.
  4. Assign project owner and collaborators.

Outcome: A scoped project exists with accountable owners.

Step 4: Run Your First Web UI Workflow​

  1. Open the project chat panel.
  2. Ask the agent to draft a delivery plan.
  3. Review generated tasks and requirements.
  4. Accept, edit, or reject outputs.
  5. Save approved artifacts to project tabs.

Outcome: Team validates an AI-assisted workflow in the Web UI.

Step 5: Configure Governance Defaults​

  1. Open Settings -> Governance.
  2. Enable approval checks for high-impact actions.
  3. Set default speed/quality tier for the tenant.
  4. Restrict sensitive capabilities to trusted roles.

Outcome: Safe operating defaults are enforced.

Step 6: Connect Essential Integrations​

  1. Open Connectors.
  2. Add one collaboration connector and one engineering connector.
  3. Test each connection in a non-production project.
  4. Document owner and purpose for each connector.

Outcome: Cross-tool workflows are enabled with ownership.

Step 7: Enable Developer Access (API/SDK/CLI)​

  1. Create API credentials in admin settings.
  2. Validate a read-only API call.
  3. Run a small SDK script for project listing.
  4. Configure CLI automation for a low-risk task.

Outcome: Programmatic access is ready without broad write exposure.

Step 8: Launch Readiness Review​

  1. Confirm role mappings and approvals.
  2. Confirm backup and restore procedure.
  3. Confirm integration permissions.
  4. Confirm monitoring and support ownership.

If all checks pass, move your first workflow to production usage.