Skip to main content

Your first environment

An environment is a fully isolated workspace in SixDegree with its own entities, integrations, AI settings, and user access. Nothing leaks between environments.

What an environment contains​

Each environment is independent. When you switch environments, every piece of data changes.

Knowledge graphDiscovered entities and their relationships.
IntegrationsConnected systems like Salesforce, Zendesk, GitHub, and more.
MCP toolsModel Context Protocol endpoints exposed to the AI.
Chat conversationsAI chat history and context.
UsersAccess control: who can view and manage this environment.
AI model settingsWhich AI models are available and configured.
VisualizationsCustom renderers for entity data.
API tokensEnvironment-scoped authentication tokens.
info

Entities discovered in one environment never appear in another. Chat history, users, and configuration are all environment-specific.

Creating an environment​

When you first log in to the SixDegree dashboard, you'll be prompted to create your first environment.

info

Screenshot needed: First-run environment creation modal: single text field labeled "Environment name" with format guidance ("Lowercase letters, numbers, and hyphens"), and a Create environment button.

Naming your environment​

Use a short, descriptive identifier, typically lowercase with hyphens.

production
staging
dev-sandbox
team-platform

Lowercase letters, numbers, and hyphens only; no spaces or special characters.

Once created, you'll be redirected to your environment's dashboard.

tip

Name environments after their purpose or team, not after yourself. team-platform and prod are easier to manage at scale than craigs-env.

Common environment patterns​

  • By lifecycle: production, staging, dev
  • By team: team-engineering, team-security, team-platform
  • By project: project-apollo, product-billing
  • By customer: customer-acme, customer-globex

Environment dashboard​

Your environment dashboard shows:

  • Knowledge graph: Visual map of discovered entities and relationships
  • Chat interface: AI assistant with context about your environment
  • Settings: Configuration, integrations, and access control

An empty environment has no entities. The next step is installing integrations to start discovery.

User roles per environment​

Users can belong to multiple environments with a different role in each.

  • Owner: full control of the environment, including managing members and deleting it.
  • Admin: invite and remove members, change roles, and configure integrations.
  • Member: use the agent and view entities and rules. Can't change environment settings.

Roles are environment-scoped: someone can be an Admin in a dev environment and a Member in production. Access is granted per environment, not globally.

Deleting an environment​

warning

Deleting an environment is permanent and cannot be undone. All entities, chat history, integrations, and configuration are lost immediately.

On the admin Environments page, click the delete icon next to the environment you want to remove. You'll be asked to confirm, and the deletion requires re-authentication with MFA step-up.

Troubleshooting​

Can't create an environment: Confirm your plan allows another environment and that you have permission to create one.

Environment not showing: Refresh the dashboard and check the environment selector in the top nav, and confirm you're signed in with the correct account.

Slow to load: This isn't expected. If an environment is slow to load, report it so we can investigate.

Next steps​