> ## Documentation Index > Fetch the complete documentation index at: https://app.keystroke.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Manage projects > Create projects, invite teammates, and manage settings. Projects you've joined appear in the sidebar of the web app. Each project has a dedicated view with tabs for the resources and settings around that project: | Tab | What you can do | | --------------- | ----------------------------------------------------------------------------------------- | | **Overview** | Browse the project's agents, workflows, skills, etc in one table | | **Repository** | View the directory from the latest deployed artifact | | **Members** | Add, remove, and update project members | | **Deployments** | View deployment versions, who deployed them, and which version is active | | **Settings** | Update name, slug, description, default role, invite permissions, and danger-zone actions | The project header includes quick actions for inviting members, renaming the project, copying the project ID, copying the project URL when available, and deleting the project. Use the Settings tab to leave a project. ## Create a project Create projects from the web app or the CLI. New projects are inactive until you deploy code to them. ```bash theme={null} keystroke projects list keystroke projects create --name "Support automations" ``` Project slugs are generated from the name and are used by CLI commands such as `--project support-automations`. See the [CLI reference](/cli#deploy) for the full command list. ## Members and access Project membership controls who can see and work in a project. Org admins can see every project in the organization; other members see the projects they belong to. Project members have one of two roles: | Role | What they can do | | ----------------- | --------------------------------------------------------------------- | | **Project Admin** | Read, deploy, update settings, delete the project, and manage members | | **Builder** | Read the project and deploy changes | Invite teammates from the project members page or with the CLI: ```bash theme={null} keystroke projects members list --project support-automations keystroke projects members invite --project support-automations --email ada@example.com --role builder ``` Only organization members can be added to a project. If someone is not in the organization yet, invite them to the organization first. ## Project settings Project admins can update the project name, description, default member role, and who is allowed to invite members. ```bash theme={null} keystroke --project support-automations project update --name "Support agents" keystroke projects settings update --project support-automations --default-role builder keystroke projects settings update --project support-automations --invite-permission admin ``` Use project settings for collaboration boundaries, not for runtime behavior. The codebase still defines what agents, workflows, triggers, actions, skills, and files the project can run. ## Project credentials Credentials can be scoped to a project. Use project-scoped credentials when every agent and workflow in the project should share the same connection, such as a Slack workspace, Linear workspace, or API key. ```bash theme={null} keystroke credentials create exa --scope project --project-slug support-automations --set apiKey=@env:EXA_API_KEY ``` Project credentials are available to the code that runs in that project. If different teams or environments need different credentials, put them in separate projects or set separate credential instances. See [Credentials](/learn/credentials/overview). ## Delete or leave a project Project admins can delete a project. Deleting a project removes the project and its platform state, so treat it as a destructive operation. ```bash theme={null} keystroke --project support-automations project delete --yes ``` Members can leave a project when they no longer need access: ```bash theme={null} keystroke projects members leave --project support-automations --yes ``` ## Next steps Understand how projects organize automation work. Build and deploy the codebase behind a project. Connect project-scoped credentials for agents and workflows. Inspect what has run in a project.