Set up a tenant

This section takes a new tenant from an invitation link to its first real batch on HubSpot. It’s written for the tenant’s owner: the person who connects the CRM, decides who approves what, and keeps the motions in a repository. If you haven’t yet, run the Quickstart first; it’s the fastest way to see what each step below is for.

Who does what

Who	Does
Pruma	Creates the tenant, names its first owner, and sends the invitation link.
You, the owner	Join, create the repository, connect HubSpot, add provider keys, invite your team, and open the first batch.
Your team	Answer the questions in their queues, and approve changesets if they’re approvers.

The checklist

1. Join your tenant. Open the invitation link, create your account, and check your handle.
2. Create the tenant repository. The folder that holds tenant.yaml, crm.yaml and your motions, with the command line tool installed and an API token to push with.
3. Connect HubSpot. Map your HubSpot properties in crm.yaml, push, and paste a private-app token in Settings → CRM.
4. Add provider keys. The built-in sources need a key per provider, either yours or Pruma’s. Custom sources need their secrets.
5. Invite your team. Give each person a role and a handle that matches the approvers and queue owners in your motions.
6. Publish from GitHub. Push the repository to GitHub so merges to main go live, and connect it so edits made in the app come back as pull requests.
7. Go live. Turn fixture mode off, rehearse on a small list, then open the first real batch.

Where you can get stuck

A few of these steps depend on things that aren’t finished in the platform yet: the command line packages aren’t on npm, HubSpot is read-only, and invitations aren’t sent by e-mail. Each page says where, and Limitations lists them all.

Join your tenantStep 1: the invitation link, your account and your handle.