Getting Started
This page describes the first-run path for joining an enterprise-managed Caracal environment without exposing private deployment details.
Audience: Enterprise end users and administrators
Before You Start
Have the following ready:
- enterprise access details from your organization
- a runtime or workspace that is allowed to connect
- the approved enterprise connection endpoint or connector instructions
- the credentials or token material your organization uses for that first connection
First-Time Workflow
1. Sign in or accept your invitation
Start by completing your organization’s enterprise sign-in or invitation flow. This confirms that you are joining the correct organization context before connecting any runtime or workspace.
2. Connect the runtime or workspace
Use the approved enterprise connector path to attach your Caracal runtime or workspace to the enterprise environment. The connected runtime stays responsible for enforcement, while Enterprise adds shared administration and visibility.
3. Confirm the connection state
After the initial connection:
- verify that the workspace appears in the expected organization context
- confirm that the connection is recognized as enterprise-managed
- check that the expected team members or administrators can see the environment
4. Review initial access and ownership
Before broader rollout, confirm:
- the right people have the right roles
- the workspace belongs to the intended organization
- the environment is ready for normal operations
5. Run a simple operational check
Use a low-risk validation step, such as viewing workspace status or checking recent activity, to confirm that the connected environment is behaving as expected.
What Changes After Connection
Once connected, teams typically gain access to shared enterprise workflows such as:
- centralized administration
- team and role management
- enterprise monitoring views
- workflow or reporting surfaces that depend on enterprise features
Common First-Day Checks
- Confirm sign-in works for the expected users.
- Confirm the correct organization or workspace context is selected.
- Confirm the runtime reports as connected.
- Confirm the team can reach the intended administration and monitoring pages.