Assign setup and ongoing responsibilities

Agree who owns each part before starting setup. One person may hold several roles. Employees who only use finished tools do not need Google Cloud access or a paid Applane seat.

Company setup

Role	Access needed	Responsibility
Applane owner or admin	Company Google account and Applane admin access	Create the account, collect configuration values, run checks and manage building access. Owners also manage billing.
DNS owner	Permission to edit the company’s DNS	Add the verification TXT record.
Google Cloud or Platform admin	Permission to enable APIs and update project IAM; billing access for budgets	Configure the project, builders group IAM grant, OAuth client and budget alerts.
Workspace admin	Relevant Google Admin console permissions	Check Apps Script, create groups and any publishing bot, set sharing policy and manage offboarding.

Create the builders group before granting it project access. DNS verification can run while the other setup work is in progress. The setup path links to each team’s instructions.

After setup

Role	Responsibility	Guide
Employee building a tool	Describe the task, test it and publish reviewed changes.	Build your first tool
Tool owner	Handle questions, access requests and maintenance; arrange a backup editor.	Sharing, maintenance
Manager or team lead	Choose the first task, test with colleagues and review whether it helps.	Team rollout
Leadership or budget owner	Agree the rollout scope, ownership and budget with IT and the team.	Pricing, budget alerts
App user	Use the published link with the correct work account; report issues to the tool owner.	Use a shared tool

Allow about an hour for setup when one person has all the required access. Split ownership can add approval and scheduling time; confirm those handoffs before promising a rollout date.