From 14356e5431dd01e4ec493a142e632dbe1016ab86 Mon Sep 17 00:00:00 2001 From: hcarreras Date: Tue, 26 May 2026 12:10:01 +0200 Subject: [PATCH 1/2] Add Claude setup It needs an organization, so instructions are needed. --- ...roject.md => Client_infrastructure_setup.md} | 17 +++++++++++++++-- tools_and_services/access_and_permissions.md | 9 +++++++++ 2 files changed, 24 insertions(+), 2 deletions(-) rename project_management/{Technical_setup_when_starting_a_new_project.md => Client_infrastructure_setup.md} (83%) diff --git a/project_management/Technical_setup_when_starting_a_new_project.md b/project_management/Client_infrastructure_setup.md similarity index 83% rename from project_management/Technical_setup_when_starting_a_new_project.md rename to project_management/Client_infrastructure_setup.md index 97552ed0..85bdd250 100644 --- a/project_management/Technical_setup_when_starting_a_new_project.md +++ b/project_management/Client_infrastructure_setup.md @@ -1,8 +1,10 @@ -# Technical setup when starting a new project +# Client infrastructure setup ## General -When starting a new project for a client, we try to be consistent with resource allocation. +This runbook covers provisioning client infrastructure — Github, Heroku/Azure, Claude, 1Password, Google Groups. Most of it is done when starting a new project, but the same steps apply later in the project lifecycle whenever a client needs a new service (e.g. adding Azure or Claude to a project that has been running for years). + +We aim to be consistent with resource allocation across clients. You can read more about basic rules & culture surrounding these resources in [Access and permissions](https://inside.abtion.com/tools_and_services/access_and_permissions). @@ -115,3 +117,14 @@ The goal of the setup is to have the client owning their own directory with bill - add email of each team member as contributor 4. Update the Asana licenses overview as per [Purchasing licenses and memberships](https://inside.abtion.com/tools_and_services/purchasing_licenses_and_memberships) - If it is using "abtion-general-subscription", add a due date on an estimate on when you believe the subscription should be transferred to the client. Bear in mind that Abtion will be paying for the client's subscription until then. + +## *5. Claude setup (NOT relevant for all projects) + +Only needed when we will build agents or provision API keys on `platform.claude.com` on behalf of the client. The Claude Code / claude.ai coding subscription is unrelated — it is included in our options and description and billed separately at our normal pricing. + + +1. On `platform.claude.com`, create a new organization named `[clientname]` (matching the team's google group). +2. Invite the client as `admin` of the organization. +3. Add the client's credit card as the organization's payment method (unless not yet possible — in which case use Abtion's card and create an Asana ticket to transfer billing, as per the Preparation step). + +You need to create the organization from the team account. It is not possible to create it from your personal account, as you'll be already part of Abtion's organization. diff --git a/tools_and_services/access_and_permissions.md b/tools_and_services/access_and_permissions.md index f59bf419..ba0c5480 100644 --- a/tools_and_services/access_and_permissions.md +++ b/tools_and_services/access_and_permissions.md @@ -60,6 +60,15 @@ You can request access to teams through Slack in #access-and-permissions. You can request access to teams through Slack in #access-and-permissions. +## Claude (platform.claude.com) + +This applies only to `platform.claude.com` (the Anthropic Console used for API keys and agents). The Claude Code / claude.ai user subscription for day-to-day coding is a separate matter, included in our options and description and billed to the client at our normal pricing. + +- Every client that needs API keys or agents has their own Claude organization, named after the team's google group. E.g. `danish-shipping`. +- The client is invited as `admin` of the organization, and their credit card is used for all API and agent usage. Costs can add up quickly, so this must not flow through Abtion's account. + +You can request access through Slack in #access-and-permissions. + ## Managing accounts: - Keep the [license overview](https://app.asana.com/0/1149529931138025/list) up to date. This will help us track the activity on services and licenses as well as make it easier to downgrade/upgrade when needed. From f097c38275b329beddf3ea8a3854eb73c5f62ff5 Mon Sep 17 00:00:00 2001 From: hcarreras Date: Tue, 26 May 2026 16:25:44 +0200 Subject: [PATCH 2/2] Remove client-specific references --- tools_and_services/access_and_permissions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tools_and_services/access_and_permissions.md b/tools_and_services/access_and_permissions.md index ba0c5480..d83c6e4d 100644 --- a/tools_and_services/access_and_permissions.md +++ b/tools_and_services/access_and_permissions.md @@ -34,7 +34,7 @@ You can request access to vaults through Slack in #access-and-permissions. ## Google groups -- A google group will be set up per client, e.g. `danish-shipping@abtion.com`. +- A google group will be set up per client, e.g. `name-of-client@abtion.com`. - The group will be used for creating client-specific accounts for services such as github, azure, etc. ## Github @@ -42,7 +42,7 @@ You can request access to vaults through Slack in #access-and-permissions. - Access is controlled through teams. Abtioneers are part of teams. Teams have access to repos. E.g. Wordpress team will have access to several repos. - To give a better overview, members should not be granted direct access to any repo. - The Abtion team has read access to all repos. All Abtioneers are members of the Abtion team. -- Every new client with a developer team will have their own Github team. E.g. `danish-shipping`. +- Every new client with a developer team will have their own Github team. - Every client has a github account - using the team's google group. This account is added as a member of the client team. - Several teams may have access to the same repos. E.g. The Digital Infrastructure team may have access to some clients' repos while they are on maintenance. @@ -64,7 +64,7 @@ You can request access to teams through Slack in #access-and-permissions. This applies only to `platform.claude.com` (the Anthropic Console used for API keys and agents). The Claude Code / claude.ai user subscription for day-to-day coding is a separate matter, included in our options and description and billed to the client at our normal pricing. -- Every client that needs API keys or agents has their own Claude organization, named after the team's google group. E.g. `danish-shipping`. +- Every client that needs API keys or agents has their own Claude organization, named after the team's google group. - The client is invited as `admin` of the organization, and their credit card is used for all API and agent usage. Costs can add up quickly, so this must not flow through Abtion's account. You can request access through Slack in #access-and-permissions.