How to see and respect every user's consent

In this lesson

1. 1Scan the sidebar for a consent entry and confirm there is none.
2. 2Open Users, open one user, and go to the Privacy tab to see Consent status, Consent categories and Legitimate interest.
3. 3Open a journey, go to Journey Settings and pick a category on the Consent card.
4. 4On an email or SMS step, override the consent category or leave it on Use journey defaults.

Setup checklist

The 15 steps to run Intempt for a team, from consent to the right access for every teammate. Tick them off as you go; your ticks stay in this browser.

0 of 15 ticked

1. 1.Scan the sidebar for a consent entry and confirm there is none.
2. 2.Open Users, open one user, and go to the Privacy tab to see Consent status, Consent categories and Legitimate interest.
3. 3.Open a journey, go to Journey Settings and pick a category on the Consent card.
4. 4.On an email or SMS step, override the consent category or leave it on Use journey defaults.
5. 5.Open the org and project selector at the top of the sidebar and find the Organizations and Projects levels.
6. 6.Under Projects, find the project you work in. Each project keeps its own users, events and settings, and everything in this course works inside that one project.
7. 7.Open Users and see that the people listed belong to this project; another project would have its own list.
8. 8.From the account menu, open Settings > Domains and see that domains are verified at org level, then assigned to projects with Manage project access.
9. 9.Open Org Settings > Roles and look at the Org roles, Project roles and Custom tabs.
10. 10.Open Org Settings > Team, click Invite member, enter a real or plus-address email and choose the lowest sensible access level, for example Org member.
11. 11.In the same invite, under Project access, pick a project and give a different role, for example Project admin, then send.
12. 12.Confirm the member's org role and project role are different values.
13. 13.Open Analytics > Boards and switch to the MRR and Subscribers tabs.
14. 14.Look at the sidebar again and confirm there is no separate Subscription row.
15. 15.Open Integrations and confirm the Stripe source is connected; without it the board has no data.

Your tech stack and tools

The core stack (everything you actually need)

• Intempt console (This is where consent, projects, teammates and revenue live)
• Org admin or owner access (This is the access you need to invite teammates and change roles)
• Stripe account connected as a source (This is what fills your revenue board. Without it the board stays empty)

Highly recommended optional upgrades that level up your work

• Consent tracking via the SDK consent() method (This is how each person's consent reaches Intempt)
• A domain you own (This is how you verify your company domain once and use it in any project)
• A second email (plus-address) (This is how you can test an invite on your own)

Everything in this course works on the free plan, inside the one project you already have.