Skip to content
Current/ Help Center

Invite a partner to the client portal

5 min read · Updated Jul 17, 2026

A partner is an external person — your client — who gets a slim, read-only window into only the projects you choose to share. They see status, timeline, milestones, task progress, shared documents, and a conversation thread with your team. They never see an hour, a rate, or anything else in your workspace. Portal viewers are free and unlimited: they never count toward your bill.

The Partners page. Invite the contact, then share individual projects — a partner sees nothing you haven't shared.

This is the answer to the two emails every MSP gets every week — "where are we on the migration?" and "what's left?" — without giving a client a login that could reach your numbers.

Send the invitation

  1. 1
    Open Partners in the sidebar (under Manage)
    You'll see the partner directory. The page is limited to admins and project managers — anyone else gets an access-denied screen.
  2. 2
    Click Invite partner
    Enter the partner's email address — the one they'll sign in with.
  3. 3
    Choose the projects to share
    You get a searchable checklist of every project in the workspace (templates are excluded). Tick one or more. At least one is required — an unscoped partner account would sign in and see nothing at all, so Current won't create one.
  4. 4
    Check the visibility summary, then Send invitation
    The panel below the checklist spells out exactly what they will see and what they will never see, so you can read it back to the client before you send.
  5. 5
    Copy the join link if you'd rather send it yourself
    Current emails a branded invitation with an "Accept invitation & set password" button. Delivery is best-effort, so once the invitation is created the dialog also shows the join link with a Copy button. If email isn't configured yet, that link is your guaranteed path — paste it into your own message.

When the partner accepts, they set a password, sign in, and land straight in the portal with every project on the invitation already shared with them. Staff never see the portal by accident, and partners never see the staff app: the two shells are separate.

Note
Who can do what here
Creating a partner invitation is a Tenant Admin action — a project manager who tries gets a "Not authorized" error straight from the database. Project managers can still open Partners and share or unshare projects with partners who already exist. Pending invitations are visible to admins only. A project manager sees the panel but it always reads "No pending partner invitations" — the invitation records themselves are admin-only at the database layer. See "Roles & permissions: who sees what".

Invitations expire — and can be revoked

Every invitation is good for 14 days from the moment you create it. Until it's accepted, an admin sees it in the Pending partner invitations panel on the Partners page, showing the invited email, how many projects it carries, and the expiry date.

  • Not accepted in time? Create a fresh invitation — expired links stop working on their own.
  • Sent to the wrong address, or the contact changed jobs? Click Revoke. The link stops working immediately and they can't sign up with it.
  • Revoking is not destructive — you can invite the same person again at any time.

Change what a partner sees, later

Sharing is per project and completely reversible. Nothing is "all projects" for a partner — if there's no membership on a project, the project does not exist as far as their session is concerned.

  1. 1
    Open Partners and click the person's row
    The row shows their name, their email and domain, and how many projects they currently see. The row action reads Manage access.
  2. 2
    Toggle projects on or off
    Tick a project to share it; untick to remove it. Each toggle saves immediately — there's no Save button to forget.
  3. 3
    Confirm the effect
    Unsharing cuts their access off right away, at the data layer. If they still have the project open, their next load shows "This project isn't available — it may not be shared with you, or the link is out of date."
Heads up
Ending access completely
Removing every project leaves the partner with an account that can see nothing — usually what you want when an engagement ends. To switch the account off entirely, open Users & roles (under Admin), find them, and Disable. They lose access instantly and their comments stay intact and attributed. See "Invite team members and assign roles".

The weekly digest (optional)

Once a project has partners on it, you can have Current email them a short weekly update so they don't have to remember to log in. Open the project, scroll to the manager-only project access panel, and switch on Weekly partner digest for that project. It goes out every Monday.

  • It goes only to partner members of that specific project — never to a list you don't control.
  • It carries project status and overall progress, milestones reached in the last 7 days, the next few milestones, done-vs-total task counts, and the next few tasks by name — no assignees, no hours, no money, ever.
  • "Send me a preview" emails the digest to you and only you, so you can see exactly what the client will get before you turn it on.
Tip
Comments reach your team where they already work
The portal's conversation is a partner's only write capability, and the database forces every partner post to co-managed — partner-visible by definition, never an internal-only note. If the project is mapped to a Teams channel, partner comments mirror into that thread, clearly attributed as partner-authored. (Current posts the mirror under a connected staff member's Microsoft identity — the project lead if they're connected — so at least one staff member must have connected Microsoft 365.) See "How Teams channels work inside projects".
Note
Partner logins are a signal, not just a login
Current records a partner's portal login once a day as an engagement signal on the account — quiet evidence of whether a client is actually following the work.

For the exact contract of what the portal exposes, read "What partners can see — and what they never can" — it's written to be shown to a client. For how the restriction is enforced, see "The partner financial firewall".

Was this helpful?