Give your AI its own login in ClickUp, Slack and HubSpot

You wouldn't hand a new hire your own password. You'd give them their own login, with access to only what they need. Your AI should get the same.

On your login, your AI moves tasks, posts in chat and edits deals as you, and it sees everything you see.

This guide gives it its own limited user in ClickUp, Slack and HubSpot. You can see what it did and switch it off without touching your account.

Do it with Claude

Let Claude coach your setup

It walks you through each click and checks what you read back.

Copy
Paste into Claude
Answer, click along

Use a computer. Sign in as the AI user in a private window, so your own login stays separate.

See the prompt Claude gets

You are my setup coach. I run a small business and do not code. Use plain words and short sentences. The guide is pasted under this prompt. Use it as your script and your source of facts. I am reading it too, so do not summarize it and do not read all of its steps back to me. The guide mentions a card at the top, screenshots, and steps that tell me to paste a prompt. Ignore those: this message is that card, and I already pasted it. Task: help me give an AI its own limited user in my tools. You cannot click in my admin screens or see my screen, so give me one click at a time and check what I read back. Start with 3 to 5 basic questions, as clickable choices if you can (in Claude Code, use the AskUserQuestion tool), else lettered options: which tools, the plan and my admin role on each, whether my Claude plan is paid, and whether I have a spare Gmail or Outlook address that is not on my company's domain. I can always type my own answer. Then ask numbered follow-ups, 3 at most per message. Do not move on until you are fully clear. Never invent. Mark gaps (check). Before you give me steps, play back what you understood and wait for my yes. After 8 questions (count every question you ask me in this whole chat; do not restart the count for each tool), pause, ask if we should continue, and wait for my answer before you do anything else. If I say "enough, give me the steps", stop asking and show the steps, with gaps marked (check). Work on one tool at a time. Start with the tool my AI will touch most, then do the others. For ClickUp, Slack and HubSpot, follow the guide's steps for that tool, including the private-window sign-in and the seat-cost table. For any other tool, apply the guide's four rules: a separate user, least access (no admin, no delete), a history I can read, and one switch to turn it off. Tell me to keep this chat open in my normal window and do the steps in the private window. Go one step at a time and wait for me to say "done". Say what my screen should show. Before I approve a connector, ask me to read back the account name on the approval screen. If you are not sure what my screen shows, ask for a screenshot, and tell me to hide any emails or names first. Remind me to check seat costs before each invite, again right after the invite (before I share or connect anything), and once more after I connect the tool. In ClickUp, tell me to skip the API token, as the guide's step 11 says. For the guide's test prompts, ask me for any curly-brace values first. Never ask for passwords or API keys. Warn me about costs and ask first. Start now: put your first basic questions in this same reply, not just a promise to ask them. Use the guide's menu and button names word for word, not your own. Do not wait for me to say go.

When you copy, the whole guide goes in under this prompt, so Claude has every step.

Rather do it by hand? Jump to the steps

01 / 07

Before you start

A connector links Claude to a tool, and Claude gets the access of whichever account signs in to it. Sign in as you and it gets your access. Sign in as the AI user and it gets only that user's limited access (Anthropic).

A connector belongs to your Claude account. The sign-in you connect is used on the web, in the desktop app and in Claude Code until you disconnect it (Claude Code docs). On Team or Enterprise, a Claude Owner may need to turn a connector on first (Anthropic).

Get a spare email

The AI user needs its own email address, because ClickUp invites people by email. Create a free Gmail or Outlook address before you start. Don't use one that ends in your company's web address, because addresses on your own domain become paid limited members. Name the user AI Assistant in every tool.

Give the spare email its own password and turn on two-step sign-in. It now holds the AI's access.

Check the seat cost

An extra user can count as a paid seat. Check your own billing page after you add the user.

User type	Cost on 2026-09-30
ClickUp view-only guest	No fee on paid plans, view only. Give it Comment, Edit or Full edit and it becomes a permission-controlled guest, priced like a member unless your plan still has a free guest seat of that type
ClickUp limited member	Paid. Unlimited $7 per user per month annual, $10 monthly. Business $12 annual, $19 monthly
Slack member	Billed when active in a 28-day window. Rate is on your Slack billing page
HubSpot View-Only Seat	Free and unlimited
HubSpot Core Seat	Paid. Rate is on your HubSpot plan page

Connect a tool as the AI user

Do these steps once per tool, after you create the AI user in it. Connectors work on every Claude plan, Free included. On Team and Enterprise, an Owner has to turn a connector on for the organization first (Anthropic).

Open a private window (Incognito in Chrome).
In that window, sign in to the tool as AI Assistant.
In the same window, go to claude.ai and sign in with your own Claude account.
In the side panel, click Customize › Connectors › Discover.
Search for the tool.
Click Connect to Claude.
Read the account name on the approval screen. If it says AI Assistant, approve. If it shows your name, cancel and repeat step 2.

You should see the tool listed as connected in Claude.

Using another tool

ClickUp, Slack and HubSpot have full steps below. For any other tool, apply the same four rules:

Separate user. Give the AI its own user, never your login.
Least access. Security teams call this least privilege. No admin, no delete. Share only what the job needs.
A history you can read. Find where the tool shows what that user did.
One switch. Know how to turn that user off without touching yours.

02 / 07

ClickUp

At a glance

Role: View-only guest
Cost: No fee on paid plans
Watch: Can become a paid seat once it gets Comment, Edit or Full edit

ClickUp's Claude connector is limited to what your assigned user account allows. You sign in through ClickUp, so Claude never sees your password. As of September 2026.

Click your Workspace avatar (top left), then People.
Enter the spare email.
Pick the role. Start with a view-only guest (no fee). Use a limited member only if the AI must comment. That is a paid seat.
Click Invite people.

Limited members and guests see nothing until you share it with them. ClickUp has four levels: View only, Comment, Edit and Full edit.

In the private window, open the spare inbox and accept the invite.
Set the name to AI Assistant.
Back in your own window, open the one List or Folder the AI needs (guests can't be given a Space).
Click Share.
Add AI Assistant at View only.

Connect ClickUp as the AI user, using the steps in "Connect a tool as the AI user".
Skip ClickUp's API token (Settings, Apps, API Token). The connector doesn't need one.

Every task has a running log of task activity on its right side.

03 / 07

Slack

At a glance

Role: Member in named channels
Cost: Billed when active
Watch: Members can join any public channel

Slack's Claude connector signs in as a person, so Claude acts as whichever Slack member signs in. Your Slack Workspace Owner or app manager may need to approve the connection first. As of September 2026.

Invite the spare email as a regular member. Slack bills active members, so check your billing page afterwards.
In the private window, open the spare inbox and accept the invite.
Name the user AI Assistant.
Back in your own window, add it to the named channels it needs. Leave the AI out of private channels unless it needs one.

You should see AI Assistant in the member list. Members can join any public channel, so adding it to one channel doesn't stop it reading others. Slack has no read-only member. It can post in every channel it joins.

Connect Slack as the AI user, using the steps in "Connect a tool as the AI user".

Where to see what it did: read the channel's message history for what it sent. On Pro, Business+ and Enterprise, access logs (Admin › Workspace settings › Security › Access logs) list sign-in times, IP addresses and devices, not actions. On Enterprise, audit logs record actions.

04 / 07

HubSpot

At a glance

Role: View-Only Seat
Cost: Free and unlimited
Watch: A Super Admin approves the connector first

HubSpot's Claude connector respects the permissions you set on each user. It needs a paid Claude plan (Pro, Max, Team or Enterprise) and has no delete. As of September 2026.

Open your user settings.
Create a user with the spare email. You need Super Admin or the Add and edit users permission, per HubSpot's permissions guide.
Pick the seat. A View-Only Seat is free and unlimited and cannot edit records. A Core Seat is paid.
Set permissions per object: View on Contacts and Deals, nothing on the rest.
If you use teams, limit View to that team's records.
Leave Delete off.

A pipeline limit does not hide records. On Professional and Enterprise, a Super Admin can limit who works in a pipeline, but reports and search still show those records. Use View permissions instead (steps 4 and 5). The connector respects them.

Approve the HubSpot connector first. A Super Admin does this by connecting HubSpot to Claude once under their own login (HubSpot's steps). Only Super Admins and users with App Marketplace Access can connect without that approval.
If you connected under your own login, open Customize › Connectors in Claude, open HubSpot and click Disconnect, so the AI user can take its place.
Connect HubSpot as the AI user, using the steps in "Connect a tool as the AI user".

Don't make the AI user a Super Admin to skip step 7.

You should see the new user in your user list with the seat you chose.

Where to see what it did: a Super Admin opens settings, then Account Management, then Audit Logs. It shows 30 days. Connector create and update actions appear under both the user and the Claude connector. Reads are not logged. Record changes appear on Professional and Enterprise only.

05 / 07

Check it worked

One free test in ClickUp, about 5 minutes.

Create a task called AI test in the list you shared.
In your usual Claude window or the desktop app, start a new chat.
Click + ("Add files, connectors, and more") at the lower left of the message box.
Click Connectors.
Toggle ClickUp on.
Paste this into Claude.

Free check: who is signed in

Read the ClickUp task AI test and tell me which ClickUp user you are signed in as. Change nothing.

98 characters

Claude should name AI Assistant. If it names you, redo the sign-in. If Claude can't say, use the comment test below.

Comment test: give AI Assistant Comment access to the task, then paste this. If it is a view-only guest, that makes it a paid seat.

Comment test (needs Comment access)

Open the ClickUp task named AI test. Add one comment that reads: Test from the AI user, safe to delete. Change nothing else. Then tell me which ClickUp user you are signed in as.

178 characters

After the comment test, open the task and find the comment in its activity on the right.

DiagramWho did what, and one switch

Task activity

AI Assistant added a comment9:02

You approved the draft9:15

AI Assistant moved the task9:16

Admin settings

AI AssistantActive Off

Switch off one user. Your own login keeps working.

The task history shows AI Assistant's actions under its own name, next to yours.
In admin settings, you can deactivate the AI Assistant user on its own.
Your own login keeps working.

Fig 5.2Who did what, and one switch

Now test the limit. Paste this into Claude.

Limit test

Open the ClickUp task {TASK IN A LIST YOU DID NOT SHARE} and tell me its title. Change nothing.

95 characters

It should say it can't. If it opens the task, go back to the share settings.

In the other tools:

Slack: create a channel called ai-test, add AI Assistant, then ask Claude to summarize ai-test and say which Slack user it's using.
HubSpot: create a contact called Test Contact, ask Claude to change its job title, and it should be refused on a View-Only Seat. If it works, fix the seat first.

06 / 07

What to withhold, and the monthly check

DiagramHow much access to give

ClickUp

Admin

Member

Limited memberif it must comment

View-only gueststart here

Slack

Admin

Member, all channels

Member, named channelsstart here

HubSpot

Super Admin

Core Seat, full edit

View-Only Seatstart here

Top: opens the mostBottom: opens the least

ClickUp, widest to narrowest: Admin, Member, Limited member, View-only guest. Start at View-only guest.
Slack, widest to narrowest: Admin, Member, all channels, Member, named channels. Start at Member, named channels.
HubSpot, widest to narrowest: Super Admin, Core Seat, full edit, View-Only Seat. Start at View-Only Seat.

Fig 6.1How much access to give

Always withhold these, in every tool:

Do this now0 / 9 done

The AI user is not an owner, admin or Super AdminBilling and payment pages are off-limitsPayroll and HR folders are not sharedPrivate messages and private channels are not sharedDelete rights are offOnly the project, channel or records it needs are shared, where the tool allows itNobody has typed a personal password or API token into an AI toolEvery Write/delete tools group is on Needs approval (how)

Claude's mode is Manual (or Manually approve, if Cowork is still a separate option for you)

Once a month, spend 10 minutes on access. The weekly check of what the AI did is in the guardrails guide.

ClickUp: in People, confirm AI Assistant is still a guest or limited member.
Slack: confirm AI Assistant is still a regular member, in only the channels it needs.
HubSpot: in user settings, confirm AI Assistant still has its seat, View on only the objects it needs, and Delete off.
In Claude, ask: "Which ClickUp user are you signed in as? Change nothing." It should name AI Assistant.
Remove any access it no longer needs.
Open each billing page and confirm the seat count.

To stop the AI, deactivate or remove its user. In ClickUp: People, find AI Assistant, open its menu, then deactivate or remove it. In Slack and HubSpot, do the same in your admin settings. Your own login keeps working. Also, in Claude, open Customize › Connectors, open the tool and click Disconnect.

Finish line

What to do next

Pick the one tool your AI touches most. Open its chapter and do every step. Set aside 25 minutes. Give it less than you think it needs. You can always add access later.

You reached the end of the guide