Skip to main content
Install Tightknit in your customer community workspace: the one customers, partners, and users join. Not the internal workspace your employees work in.

​
Why

Tightknit treats the workspace it is installed in as the community:
  • The workspace roster is the member roster. Every user who joins gets a member profile, and community site sign-in is matched against those profiles. Install internally and your member directory is your staff directory, while customers outside that workspace cannot sign in until an admin adds them as members. See Who can sign in.
  • Channels are wired for publishing. Activating a channel and connecting a Feed puts its messages on your community site, which can be public and indexed. Internally, #revenue sits in the same channel picker as everything else.
  • Member count sets your pricing tier. Tightknit meters the workspace’s active member count, so an internal install bills against your headcount.
  • Analytics stop working. Studio analytics separate staff from members using the team filter. Internally, everyone is a teammate.

​
How to tell which is which

A workspace that scores in both columns is an internal workspace with a few customers in it. Create a separate one.

​
Enterprise Grid

Both workspaces usually sit under one organization. Install per workspace: an org-wide install does not create a community.
1

Install into the community workspace

Go to slackapp.tightknit.ai/slack/install, select your community workspace in the top-right dropdown, and select Allow. Do not select the organization.
2

Approve the request if your org requires it

An Org Owner or Org Admin approves it under Integrations > Requests. Approve Tightknit for the community workspace, not for all workspaces.
3

Verify

Open the Tightknit App Home in that workspace. Setup modules mean it worked. “Tightknit isn’t set up for this workspace” means the install landed elsewhere.
An org-wide install makes Tightknit available across your workspaces but creates no community: feeds, posts, events, and member management stay unavailable. If no workspace in your organization has Tightknit yet, the installing admin should also receive a DM with a link to the workspace-level install. Either way, the steps above are what create the community.
The Tightknit Enterprise Slack app is a separate, org-level app for Slack admin operations. It does not replace the workspace install.

​
Installed in the wrong workspace

A community is bound to one Slack workspace and cannot be repointed. Installing elsewhere creates a second, separate community.
1

Contact us before you change anything

Tell us which workspace you installed into, which you meant, and what you configured. That is what lets us say which parts can be moved.
2

Install into the right workspace

This creates a new community. The original is untouched.
3

Set up the new community

Work through Quickstart.
4

Remove the app from the wrong workspace

Tools & settings > Manage apps > Tightknit > Remove App. Do this last.
If you caught it immediately and configured nothing, skip step one: install into the right workspace and remove the app from the wrong one.

​
Internal pilots

Pilot in the community workspace with the doors closed, not in your internal workspace. Then there is nothing to migrate at launch.
1

Create the community workspace

Create Your Slack Workspace. Name and URL as though you were launching today: avoid pilot or test, since the URL becomes part of your invite link.
2

Restrict invitations to admins

Tools & settings > Workspace settings > Invitations. This keeps the pilot closed.
3

Install Tightknit and set it up

Work through Quickstart. What you configure now is what members see at launch.
4

Mark your team as teammates

Add your company email domains under Settings > Team filter. Not retroactive, so add anyone already in the workspace by hand.
5

Open the doors

Keep the site on Restricted Access while testing, then switch to Public Access, relax invitations, and invite members.

​
No community workspace yet

Create it first with Create Your Slack Workspace. Settle these before inviting anyone, because each is awkward to change later:
  • Workspace name and URL — it becomes part of your invite link.
  • Who can invite members — admins only, or all members for an open community.
  • Default channels — new members join these automatically.
  • Three to seven starter channels — including an admin-only #announcements. Some Slack plans cap admin-only channels, so set it early.
  • Message retention — Tightknit makes synced conversation searchable, so longer retention keeps more of it useful.