SuiteDash client portals that clients actually use

A SuiteDash portal gets used when a client can tell, in the first minute, why they logged in. It gets abandoned when it is a second copy of the internal CRM, or when the permissions were copied from the last client and never checked. The work is deciding who sees what, then putting one next step on the home screen.

Portal access and internal CRM are different jobs

Staff live in the CRM: companies, deals, notes, and the pipeline. Clients live in a portal: their files, their invoices, the form you actually want them to complete, the date of the next call. Those are different roles. Giving a client a staff-shaped menu does not feel generous. It feels like they opened the wrong door.

Write the two lists before you touch Circles. One list is what a client must be able to do without emailing you. The other is what must stay internal — margins, other clients, draft proposals, staff-only notes. If a record type is on both lists, split the view. Do not "just hide the menu item" and hope.

Permissions pitfalls

These are the ones that produce support tickets after the invite, not before:

• Circles copied from the last client. The name changes. The access does not. A new client sees folders, or people, that were never theirs.
• Admin for everyone on the team. Faster on day one. Later, every staff login can see every client, and you cannot tell who changed a record.
• One Circle for "clients". A coaching client and a wholesale account do not need the same home. If their work is different, their access should be different.
• Files uploaded to the company, visible on the portal. Internal working documents land in the same place as the deliverable. Test with a portal login that is not your own.

A plain-language pass at the same problem is in portal permissions in plain English. If the portal already feels cluttered, signs it needs cleanup is the shorter checklist.

Branding and the first login

Branding is not a logo in the corner while the rest of the screen still says SuiteDash in a way that makes the client think they are in the wrong product. Set the name they expect, the colours you already use, and a login URL you are willing to put in an email signature.

Then do a first login that is not yours:

1. Send the invite to a colleague, or to yourself in a private window, using a real client role.
2. Read the email as if you did not build the portal. The subject should say who it is from and what to do.
3. Complete the one action you claim is the point of the portal. Time it. If you get lost, a client will leave.
4. Confirm you cannot see another client, a deal pipeline, or internal notes.

Fix the first login before you invite the client list. A second "sorry, ignore that" email is how portals get a reputation.

What to put on the portal home

One next step, not a catalog of modules. The home screen should answer "what do you want me to do?" Examples that hold up:

• Complete onboarding — one form, not six links.
• Review and approve the current deliverable.
• Pay the open invoice, or book the next working session.
• Read the two documents that are actually current. Archive the rest out of the menu.

Menus can hold more later. The first visit should not require a tour. If you are migrating CRM data at the same time, finish the import staging checks before this home screen promises records that are not there yet.

How WrightClick sets a portal up

SuiteDash setup, implementation, and support (WrightClick) treats the portal as part of configuration, not a theme you apply at the end. The pattern we repeat:

1. Name who the portal is for, and who it is not for.
2. Map Circles to those roles. Do not clone last client's Circle and rename it.
3. Put one happy path on the home screen and test it with a non-admin login.
4. Brand the login and the shell so the client recognises you.
5. Leave staff in the CRM. Clients see their slice only.
6. Turn on automations that message clients only after that path works. New AppSumo accounts should read the day-one setup steps before those FLOWs exist.

If you want that pattern built in your account, start with the overview on SuiteDash setup and ongoing support. The full implementation package, including what Onboard and Blueprint cover for Circles and the portal path, is on the SuiteDash page.