Skip to main content
This guide follows the current Felan onboarding and dashboard.

​
Prerequisites

  • A Felan account
  • A team you created or joined
  • Access to a GitHub or GitLab account when connecting repositories during onboarding
When you create your first trial team, Felan adds $5 of non-expiring AI credit for managed-model usage. Each team owner receives this signup grant once; additional teams do not receive another signup grant. Team-provided model credentials remain independent of this balance.
1

Choose where Felan sends updates

Onboarding starts with Where should Felan send updates? Choose one communication method:
  • Slack — connect a workspace, select a channel, and send the welcome message
  • Microsoft Teams — connect the Teams workspace and channel
  • Email — use your verified login email or verify other recipients
If the team already has a communication channel, Felan can move directly to the repository connection step.
2

Connect a repository provider

Connect GitHub or GitLab and authorize Felan for the repositories your team wants it to use. For GitLab, complete project selection after authorization. Felan checks that either supported connection is active before continuing.
3

Start your first session

Choose Map this codebase, Ship a quick win, or Fix a bug as a starting point. Each template is editable, and you can replace it with any non-empty custom prompt. Submitting creates the first session and opens its session page; if creation fails, the prompt remains available to retry.
4

Review progress and follow up

Felan opens the new session and streams its transcript. The session header shows its status, and delegated agents appear with the session activity. When a conversational session is running or completed, use the composer below the transcript to clarify the request or ask for the next step.

​
Add context when you need it

The first session can start with only a prompt. Add team-level configuration as your workflows require it:
  • Knowledge for durable context, reference files, and learned memory
  • Environments for variables and credentials used by agent runs
  • Integrations for additional repositories and external systems
  • Automations for scheduled or event-driven requests
Start with a specific outcome, relevant constraints, and the evidence Felan should inspect. Continue in the same session when the next request depends on its existing context.

​
Next steps

How Felan works

Learn how Felan uses context, tools, and specialized agents.

Explore the dashboard

See where sessions and team configuration live.