Skip to main content

Documentation Index

Fetch the complete documentation index at: https://support.affinity.co/llms.txt

Use this file to discover all available pages before exploring further.

​
Immediate Value

After this tutorial, your import will be verified clean, obvious duplicates merged, and your team will be in Affinity with appropriate access. You’re ready for Tier 1.

​
Prerequisites

  • You’ve completed Tutorial 0.4 — your data is in Affinity.
  • (Admin tasks) You have the “Super Admin” role.

​
Quick-Start Roadmap

  1. Review your import history
  2. Spot-check imported data
  3. Undo if something’s wrong (act fast)
  4. Merge obvious duplicates
  5. Plan your roles and permissions structure
  6. Invite your team
  7. (Optional) Configure list-level permissions for sensitive lists

​
Why Verification Matters

The window between import and team invite is your last chance to catch problems while undo is still clean. Once your team starts editing records, undoing becomes much harder — manual edits don’t get reverted, and dependencies build up. Spend an hour here so you don’t spend a week recovering.
See How to undo imports in Affinity for the time-sensitive details.

​
Task 1: Review Your Import History

​
Context

Affinity logs every import: who ran it, when, how many rows, and the outcome. The history view is your single source of truth for what happened.

​
Action

  1. Go to Settings → Manage Imports.
  2. Confirm each import you ran appears in the log with the expected row counts.
  3. Click into an import to see: Rows created, Rows updated, Rows skipped (with reasons).
  4. Note the import IDs for anything you might want to undo.

​
Expected Outcome

You have a verified record of every import, with row counts matching your expectations.

​
📚 Help Center

​
Task 2: Spot-Check Your Imported Data

​
Context

Don’t trust counts — verify content. Open actual records and confirm the data looks right.

​
Action

  1. Open the destination list. Sort by Date created (descending) to surface newly imported rows.
  2. Open 5–10 random profiles. For each one, check:
    • Is the name spelled correctly?
    • Is the email / domain the right one?
    • Are fields populated with the values you expected?
    • Are company associations correct (for people) or person associations correct (for companies)?
  3. Spot-check from both ends of the import — first rows AND last rows of the CSV. Encoding issues sometimes hit only specific rows.
💡 If everything in your first 10 spot-checks looks right, you can confidently assume the rest is too. If anything looks wrong, expand the check before deciding undo vs fix-in-place.

​
Expected Outcome

You’ve personally verified that the import landed correctly.

​
Task 3: Undo If Something’s Wrong

​
Context

If the spot-check surfaces problems and the import is recent (within hours, ideally), undo is cleaner than fix-in-place.

​
Action

  1. Go to Settings → Manage Imports.
  2. Find the import you want to reverse.
  3. Click the “Undo import” button next to it.
  4. Confirm the action. Affinity reverses the import — created rows are deleted, updated rows are reverted.
  5. Fix the problem in your source CSV, then re-run the import.
Undo doesn’t revert manual edits made after the import. If a teammate edited an imported row before you undo, that edit may be lost. Communicate before undoing if your team has been working in the data.

​
Expected Outcome

The bad import is reversed and you can re-import cleanly.

​
📚 Help Center

​
Task 4: Merge Obvious Duplicates

​
Context

Even with careful prep, some duplicates will slip through (e.g., the same person already existed from your email sync, then got created again by the import). Affinity has a manual merge tool.

​
Action

  1. In the destination list, sort by Name alphabetically. Scan for near-duplicates.
  2. For each suspected duplicate, open both profiles in separate tabs to compare.
  3. On the profile you want to keep, click the three-dot menu → “Merge with another profile”.
  4. Select the duplicate profile to merge in. Affinity will combine fields, notes, and interaction history.
  5. Confirm the merge.
Merges are not undoable. Once you merge two profiles, you cannot un-merge them. Be sure before confirming.
💡 Don’t try to dedupe everything in one session. Focus on the obvious ones — exact name + same company. The rest can be cleaned up over time in Tutorial 11 (Data quality).

​
Expected Outcome

Obvious duplicates from the import are merged. Your data is clean enough to bring teammates into.

​
📚 Help Center

​
Task 5: Plan Your Roles and Permissions

​
Context

Before inviting anyone, decide on the role each person will get. Affinity has account-level roles (Super Admin, Admin, User) and per-list permissions (Owner, Editor, Viewer).

​
Action

  1. List everyone you’ll invite: name, email, role, which lists they need access to.
  2. Default most teammates to the “User” account-level role. Reserve “Admin” for 1–2 people who manage workspace settings; “Super Admin” for billing/owner.
  3. For each list, decide the default permission level for the team (Editor for most teams; Viewer for read-only audiences like LPs or board members).
Enterprise customers have additional permission tiers including team-level permissions. See Affinity enterprise permissions.

​
Expected Outcome

You have a written plan for who gets what access.

​
📚 Help Center

​
Task 6: Invite Your Team

​
Context

With your data verified and your roles planned, invite teammates.

​
Action

  1. Go to Settings → Users and Permissions → Users.
  2. Click “Invite User” in the top-right.
  3. Enter the teammate’s email, select their role, and (optionally) pre-assign list permissions.
  4. Click “Invite User”. They’ll receive an email and follow the same flow you did in Tutorial 0.1.
  5. Repeat for each teammate. For large teams, paste a comma-separated list of emails in the invite modal — it handles bulk invites in one go.
💡 Stagger your invites if you have a large team. Bringing 50 people in on the same day means 50 people asking you setup questions on the same day. Phase by team or role.

​
Expected Outcome

Your team has access to Affinity and can start their own Tier 0 + Tier 1 progression.

​
📚 Help Center

​
Task 7: Configure List-Level Permissions for Sensitive Lists (Optional)

​
Context

Some lists shouldn’t be visible to everyone — e.g., a fundraising pipeline visible only to partners, or an LP relationship list restricted to IR. List-level permissions override the account-level default.

​
Action

  1. Open the sensitive list.
  2. Click “Share” in the top-right (or list settings → Permissions).
  3. Change the default access to “Restricted”.
  4. Add specific users or teams who should have access, and their permission level (Owner / Editor / Viewer).
  5. Save.
Restricted lists disappear from non-permitted users’ view entirely. This is intentional — but make sure no one will be confused when they can’t find a list they expected to see.

​
Expected Outcome

Sensitive lists are properly gated.

​
📚 Help Center

​
Common Questions

Q: I invited someone but they didn’t get the email. Check their spam folder first. If still missing, go to Settings → Users, find the user, and click “Resend invitation”. Q: Can I downgrade someone from Admin to User later? Yes. Go to Settings → Users and Permissions → Users, click the user, and change their role. The change takes effect immediately. Q: What’s the difference between Editor and Viewer at the list level? Editors can add, edit, and delete entries in the list. Viewers can see entries but cannot modify them. Both can see profile data and add notes (unless you’ve further restricted those). Q: How many users can I invite? Depends on your plan. Check Settings → Billing Settings to see your seat count.

​
Where to Go Next

🎉 You’ve finished Tier 0. Your account is set up, data is in, team is invited. ➡️ Head to Tier 1: Foundation and start with Tutorial 1: Your First List.