How to share Google Ads scripts with your team

Give colleagues access to the same scripts, accounts and run history without passing code around.

In many teams, scripts live in one person's head and one person's Google login. When that person is away, nobody knows which script does what, or why a client's report stopped arriving.

A shared workspace

In chiliad, scripts belong to the workspace, not to a person. Everyone you invite sees the same:

Script library — the code, its version history and who changed what.
Accounts — which accounts run which script, with their values.
Run history and alerts — what ran, what failed, and when.

Nobody needs to copy scripts between accounts or send code by chat.

Inviting people

Open Settings → Team.
Enter one or more email addresses.
Choose a role — Member or Admin — and the access level.
Send the invite. The person accepts it and joins your workspace.

Team workspaces are available from the Studio plan, which includes up to five members. Agency includes ten and Scale is unlimited.

Working together without stepping on each other

Versions show the author. If a change breaks something, you can see who made it and restore the previous version.
Config changes are logged per account.
Alerts go to a shared Slack channel as well as to individuals.
Marketplace installs are shared. A script one person installs is available to the team.

People who belong to several workspaces

A freelancer invited into an agency's workspace keeps their own workspace too, and switches between them with the selector at the top of the sidebar. Nothing is copied between workspaces.

To limit what a team member can see, read How to limit a team member to specific client accounts.

1
Roles: the Owner controls billing and can transfer ownership. Admins manage members, accounts and scripts. Members work with scripts and accounts.
2
Access: Full access covers every account in the workspace. Private covers only the accounts that person connected.
3
Pending invites expire. Resend or cancel them here.
4
Invite several people at once and choose their role and access up front.

A shared workspace

In chiliad, scripts belong to the workspace, not to a person. Everyone you invite sees the same:

Script library — the code, its version history and who changed what.

Accounts — which accounts run which script, with their values.

Run history and alerts — what ran, what failed, and when.

Nobody needs to copy scripts between accounts or send code by chat.

Inviting people

Open Settings → Team.

Enter one or more email addresses.

Choose a role — Member or Admin — and the access level.

Send the invite. The person accepts it and joins your workspace.

Team workspaces are available from the Studio plan, which includes up to five members. Agency includes ten and Scale is unlimited.

Working together without stepping on each other

Versions show the author. If a change breaks something, you can see who made it and restore the previous version.

Config changes are logged per account.

Alerts go to a shared Slack channel as well as to individuals.

Marketplace installs are shared. A script one person installs is available to the team.