To set up Make.com for a small team, create one organisation under a business login, invite colleagues by role (Owner, Admin, Member, Accountant), authorise each connection with a shared business account rather than a personal one, and build one low-risk AI scenario first. Allow about two hours for all three.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe step that people skip is connection ownership. A scenario that runs on one employee's personal Google login stops the day that login changes. Everything in this tutorial is ordered to avoid that single failure, then to leave you with a scenario that does something useful.
What is the difference between a Make organisation and a team?
A Make organisation holds the plan, billing and users, and teams sit inside it to own the scenarios, connections and data stores. Make's help page describes an organisation as the way to structure teams, control access and manage credit and data consumption. Each organisation has its own plan and billing, so credits and data are tracked separately per organisation. A new organisation starts on the Free plan with one team, My Team.
A small firm should have exactly one organisation. Several organisations mean several bills and several sets of credits, and nobody can see usage across them. The usual cause is each person signing up on their own account and building alone; if that has already happened, pick one organisation as the home and move builds across by recreating them, because the help page says each item belongs to one team and its team cannot be changed.
Teams are for separating who can see what. A fourteen-person manufacturer might want a "Sales" team and a "Finance" team, so the finance scenarios and their connections are visible only to finance staff. The catch is plan-related: on plans below the Teams pricing plan, an organisation can have only one team, and roles within it cannot be managed. For a team of five who all see everything, one team is fine. If you need separation, check the plan first in the Make pricing tutorial.
Step 1: create the organisation under the right login
- Sign up with a business address that will outlive any single person, such as one tied to the director's account or a role mailbox you control. Time: five minutes.
- Name the organisation after the business. Names appear in invitations, so use the trading name your colleagues recognise.
- Note that you are the Owner. Make's page says the Owner is the only role that can transfer ownership or delete the organisation.
- Record the login details in your password manager, with a second person able to reach it.
Say a wholesale distributor starts with the operations manager's own address. When she leaves eighteen months later, nobody can change billing. Ownership can be transferred, but only by the Owner, so do it before departure, not after. Better still, start with a role-based login and put the manager in as Admin.
How do you invite people to a Make organisation?
Only an Owner or Admin can invite users to a Make organisation, and each person should get the smallest role that works. In the left sidebar choose Org, open the Org Users tab and click Invite user. Enter the email, name, team, role and an optional note, then save. The invitee receives an email with an "Accept invitation" button, and invitations expire after 7 days. If one expires, remove the user and send a new one.
The organisation roles, from Make's help page:
| Role | Use it for |
|---|---|
| Owner | One senior person. Full control, can transfer ownership or delete the organisation. |
| Admin | A second trusted person. Manages settings, users, teams, billing and subscriptions; cannot transfer ownership or delete. |
| Member | Colleagues who build or run scenarios. Can run and activate scenarios; team access depends on their team role. |
| Accountant | Your bookkeeper. Views billing, payment and credit information; cannot change them. |
| App Developer | Someone installing and managing apps and agents. |
| Guest | Outsiders with minimal visibility. Does not grant general access to team data. |
Owners and Admins automatically have Team Admin access in all standard teams. Within a team, the roles are Team Admin, Team Member (full access to team resources, can run and activate scenarios), Team Operator (read-only, but can activate, deactivate and schedule scenarios), Team Monitoring (read-only, including scenario and execution logs) and Team Guest. Role management inside a team needs the Teams plan, as noted above. Custom roles need Enterprise.
For an eight-person HR consultancy, a sensible starting layout is: managing director as Owner, operations lead as Admin, two staff as Members who build, the bookkeeper as Accountant and nobody else. Add people when a real job needs them. Contractors should be Members only for the length of the job and removed when it ends.
Who should own a Make connection?
A Make connection should be authorised with an account the business owns, not one a person owns, such as a shared mailbox. A connection is Make's saved link to an app such as Google Sheets, Gmail, Slack or a CRM. Make's custom-roles page describes team roles as covering team-owned resources such as scenarios, connections and data stores, so a connection lives inside a team, not on a person. What the connection authenticates as is your choice, and it is the choice that matters.
Use this rule: authorise with an account the business owns, not one a person owns.
- For email, use a shared mailbox such as a sales or accounts address in a business email system, not an individual's inbox.
- For spreadsheets, share the file with the business account and connect that account.
- For chat, create or use a bot or integration user instead of a named colleague.
Two Google-specific points from Make's Google Sheets documentation. First, the connection dialog lets you switch on advanced settings and enter your own Google Cloud client credentials instead of using the default Sign in with Google route, which is awkward for non-technical owners. Second, Make says that if your own Google Cloud project stays in Testing status, the connection must be re-authorised every week, and moving the project to In production avoids that. A recurring failure like this is a real risk behind a quote process, and both points favour one business-owned account that somebody maintains.
Name every connection so you can find it later
Connection naming pattern: [App] - [account used] - [team]
Google Sheets - ops@yourcompany - Sales
Gmail - accounts@yourcompany - Finance
Slack - Make bot - Sales
Connection register (one row each):
App | Authorised as | Owner of that account | Scenarios using it | Review date
Sheets | ops@ | operations lead | Quote sorter, Weekly digest | 1 Mar
Gmail | accounts@ | finance admin | Invoice reader | 1 Mar
The register takes ten minutes to keep and saves an afternoon the first time something fails. A distributor with six scenarios and three connections can see at once that if the accounts@ password changes, only the invoice reader is affected.
Step 4: set the billing contact and a credit alert
Billing sits with the organisation, and Owners and Admins manage it. Make your bookkeeper an Accountant so they can view billing, payment and credit information and download what they need without being able to change anything. Then agree a credit alert level between yourselves: Make credits expire at the end of the term and do not roll over, so decide who checks usage at the 70 per cent mark each month and what they do. Plan questions are in the Make pricing tutorial.
How do you build a first AI scenario in Make?
Build the first scenario around a low-risk job that runs often enough to show a result and can be checked by eye, such as sorting inbound enquiries. The scenario below takes a new row in a Google Sheet (filled by your web form), asks an AI module to classify it and write a one-line summary, writes the result back and sends a notification. Time: about forty minutes.
- Create the scenario. In your team, choose Create a new scenario and name it "Enquiry sorter - draft v1".
- Add the trigger. Use the Google Sheets row-watching trigger (Watch New Rows in the module list, though module names can change) with the business-owned connection. Point it at the enquiries sheet.
- Add the AI module. Make's own text-prompt modules do not need your own AI key, and credits are based on tokens and operations. Alternatively use an OpenAI, Claude or Gemini module with your own key, in which case Make bills one credit per operation and the provider bills tokens.
- Write the prompt. See the example below.
- Add the output. A Google Sheets, Update a Row module writes the classification back into the row.
- Add the notification. A Slack or email module tells the team about high-urgency rows only.
- Run once with a test row. Check every module's output bubble, not just the last one.
- Switch on scheduling. Start at every 15 minutes and slow it later if volumes are low; see the scheduling tutorial.
Prompt for the AI module (illustrative)
You triage enquiries for a small manufacturer. Read the enquiry and
answer with exactly two lines:
Line 1: STANDARD, CUSTOM or SPAM
Line 2: a summary of at most 20 words.
Enquiry: {{3.Message}}
Sample reply (illustrative)
CUSTOM
Wants 40 brackets in 316 stainless, hole spacing changed, needed by Friday.
What to fix: if the reply has extra words, add "no other text".
Test with a blank row and a very long one before you switch it on.
If the Google Sheet behind your first scenario is the part you want to get faster at, try The Complete Excel Course with AI Integration on Coding Liquids.
Where small teams trip up
Everyone builds in a private scratch area
Say two staff each build a copy of the same scenario under their own sign-in, and both run on a schedule. The second copy doubles the credits and sends every alert twice. The fix is one scenario in the shared team, named with the owner and version, and a rule that drafts stay switched off.
A connection is created by a contractor
A freelancer connects the company's inbox with their own login to finish the build, then leaves. Months later the connection fails. Ask for a handover where the connection is recreated with the business account, then check that the scenario runs again before they go.
Nobody is told when a scenario fails
Silent failure is the real danger, because an enquiry sorter that stops looks identical to a quiet week. Read how to stop automations breaking silently, and at minimum turn on the notification path for failed executions.
Too many people hold Admin
Admins can manage billing and users, so keep the number at two. Say a B2B software reseller has five Admins and an unknown person appears in the user list: everyone assumes someone else invited them. With two Admins, the answer is obvious.
How to check the set-up worked
- Sign in as a Member, not as the Owner. Can they run the scenario? Can they see billing? (They should not.)
- Look at the connection register and confirm each connection is authorised by a business account.
- Run the scenario with a row you know the answer to and compare the result by eye.
- Check the credit figure after the first day and compare it with your estimate.
- Ask someone who did not build it to find the scenario and say what it does in one sentence. If they cannot, rename it.
A worked layout for a fourteen-person manufacturer
Say a small manufacturer has a director, an operations manager, a sales lead with two sales staff, a finance administrator, a bookkeeper who visits monthly and eight production staff who will never touch Make. This is the layout I would set up, with illustrative names for roles only.
| Person | Organisation role | Team and team role | Why |
|---|---|---|---|
| Director | Owner | Team Admin (implicit) | Holds ownership and can sign off plan changes. |
| Operations manager | Admin | Team Admin (implicit) | Backup for billing, users and rebuilds. |
| Sales lead | Member | Sales: Team Member | Builds and edits sales scenarios. |
| Two sales staff | Member | Sales: Team Operator | Can switch scenarios on or off, cannot edit them. |
| Finance administrator | Member | Finance: Team Member | Owns invoice and payment scenarios. |
| Bookkeeper | Accountant | None needed | Sees billing and credit information only. |
Two things in this layout depend on the plan. Separate Sales and Finance teams, and the Operator role, need a plan that supports more than one team and role management, which Make's help page ties to the Teams pricing plan. If the firm is on a lower plan, it has one team, everyone is a Member and the separation is a matter of habit rather than permission. Say that plainly to the staff, because they will otherwise assume finance scenarios are hidden when they are not.
What should you do when someone with Make access leaves?
Run a handover checklist when someone with Make access leaves or a contractor finishes, because people are the main risk to a small firm's automations.
- List every scenario they built or edited, and name a new owner for each in the register.
- List every connection authorised with their personal account. Recreate each with the business account and swap it in. Make's help index lists an article on replacing connections in multiple modules across one or many scenarios, which saves editing each module by hand.
- Run each affected scenario once with test data and check the result.
- Change the role to the lowest that works, then remove the user when the handover is confirmed.
- If the leaver was an Admin, check who else can still manage billing and users.
- Note the date and the scenarios touched in the register.
Imagine an HR consultancy whose consultant built a scenario that copies new candidates into a tracker. She leaves; her Google login is closed; the scenario fails at 2 a.m. and nobody notices for nine days. With the checklist, step 2 would have caught the connection a week before she left.
What should the first month with Make look like?
Setting up Make is quick, but making it stick takes a month. This is a realistic schedule for a small team with one person leading.
- Week 1: organisation, roles, connection register, first scenario built and tested with five rows.
- Week 2: the first scenario runs live with a person checking every output by eye each morning. Record anything it gets wrong.
- Week 3: fix the prompt and the fallback value for anything the checks flagged. Add the failure notification. Read the credit use against your estimate.
- Week 4: decide whether to keep it, slow its schedule or retire it. Only then choose the second scenario.
If the first scenario is not saving anyone time by week four, the problem is usually the job chosen, not the tool. The reasoning in five scenarios a small firm can run without code can help you pick a better one.
How do you read a Make scenario's run history?
Read a scenario's run history after the Step 5 test run, because every run leaves a record and reading that record is the skill that separates a working set-up from a lucky one. After the test run in Step 5, open the scenario's history and do the following.
- Confirm the number of operations matches your expectation: four modules should show four operations on a normal run.
- Open the AI module's output and read the full reply, not the preview. Check that it is exactly the two lines you asked for.
- Open the module that wrote to the sheet and confirm the cell contents match the AI reply, with no stray spaces or quotation marks.
- Find a run that failed, if any, and read the error message. Note which connection or module caused it.
A small habit with a large payoff is to keep a short "known problems" note beside the register: "AI reply sometimes adds a full stop after SPAM, so the filter trims it." These notes are what the next person needs, and what you will need yourself in six months.
Does a small team need more than one scenario owner?
Yes, and the register should say who is the second. Each scenario should have a named owner and a named backup, both with at least Team Member access. In a six-person B2B software reseller, the sales lead might own the lead-sorting scenario with the operations manager as backup, and the operations manager might own the renewals reminder with the sales lead as backup. The backup does not need to understand every module; they need to know where the scenario is, how to switch it off and who to ask.
What should you build second in Make?
After the first scenario has run for a fortnight without surprises, copy its shape: the same trigger, AI and notification pattern covers inbound supplier emails, support queries or review replies. A ready-made template may save time, but import it carefully and check every module. If you would rather have someone else do the first build, what to check before hiring a Make expert lists the questions.
Make's roles, plan limits and module names change, so treat this as the pattern and check the help pages on organisations and teams on the day you set up. If you want to talk through your own team structure, that is what my AI implementation consultation covers; you can get in touch here.
Make.com set-up questions from small teams
How do you set up Make.com for a small team?
Create one organisation under a business login, invite colleagues with the smallest role that works, authorise each connection with an account the business owns rather than a personal one, and build one low-risk AI scenario first. Name an owner and a backup for each scenario and keep a register of connections.
What is the difference between a Make organisation and a team?
The organisation holds the plan, billing and users, and each organisation starts on the Free plan with one team called My Team. Teams sit inside it and own scenarios, connections and data stores. Each item belongs to one team and cannot be moved to another, so choose the team structure before you build.
Who should be the Owner of the Make organisation?
Use a role-based business login or the director's account, not a contractor's or a junior's. The Owner is the only role that can transfer ownership or delete the organisation. Put a second person in as Admin so that billing and users can still be managed if the Owner is away or leaves.
Why does a connection break when someone leaves?
Because it was authorised with that person's own login or token. If their account is closed or their password changes, the scenarios using the connection fail. Authorise connections with a shared business mailbox or service account, and note in a register which scenarios use each one.
Can I add a bookkeeper who only sees billing?
Yes. Make's Accountant organisation role can view billing, payment and credit information without changing billing or settings. Invite them with that role instead of making them an Admin. Invitations expire after 7 days, so remove and resend an expired one.
Further reads
- How to Build Your First AI Automation in Make, Step by Step — Another walk-through of a first AI automation.
- Zapier vs Make vs n8n for AI Automation: Which Fits Your Business? — Check Make is the right tool for the job.
Browse all AI-for-business tutorials
Sources: Make help pages on organisations, teams, custom roles and credits, and Make's pricing page, read on 17 November 2026.
