WORLDs Power-Up

Assign CRM Targets (Contacts and Companies) to one or more WORLDs, and Staff outside those WORLDs won’t see them or their associated Projects, Deals and Documents. Targets can join a WORLD when they’re created, through a Form’s assignments, an Auto-Template, the Add to WORLDs automation or a CSV import, or in bulk from Manage WORLDs by adding Contacts, Companies or the current members of a Circle. A Global WORLDs setting can also hide every CRM Target that isn’t assigned to a WORLD.

For example, an insurance agency runs a personal lines team and a commercial lines team. Every quote request from its commercial Form lands in the Commercial WORLD automatically, so the personal lines agents never see those businesses, their Deals or their Documents. Each team works a CRM that holds only its own clients, and nobody has to sort new leads by hand.

Once your WORLDs exist, a WORLD(s) section appears on your assets: Forms, Document Generators, Task Templates, Project Generators, invoice and Estimate Generators, Drip Sequence Templates, Auto-Templates, FLOWs, Email Cannons and many more. Assign an asset to one or more WORLDs and only Staff in those WORLDs can access or edit it. That prevents accidental edits and cross-team mix-ups on the resources your business depends on.

For example, a law firm assigns its engagement letter Document Generator and its retainer Recurring Invoice Generators to a Partners WORLD. Paralegals still use their own Task Templates every day, but they can’t open or change the firm’s contract templates or billing setup, so a well-meaning edit never reaches a client’s engagement letter.

Give a freelancer, contractor or partner firm a Staff login and place them in their own limited-access WORLD, where they see only the CRM Targets and assets you assign to it. Force & Hide keeps that WORLD always active for them. With the Global WORLDs settings turned off, CRM Targets and assets that aren’t assigned to any WORLD stay hidden too, so nothing slips through the gaps.

For example, a marketing agency hires a freelance copywriter for three clients. The agency creates a Copywriter WORLD, adds those three Companies and its content brief Form, and adds the copywriter as Staff. The copywriter works inside the agency’s portal but never sees its other clients, its pricing Generators or its internal Automations.

Create a WORLD for each department, such as Marketing, Billing, HR or Sales, and add its people one by one or a whole Team at a time. Give each WORLD its own Forms, Generators and Automations (Auto-Templates, FLOWs, Schedules, Drip Sequence Templates and Email Cannons), and scope Webhook Templates to a WORLD so one automation sends a different payload depending on the Contact’s WORLD. The Super Admin, and any Admin Manager you allow, keeps the full view through the Super WORLD, which sees every Contact and asset.

For example, a growing accounting firm sets up Tax, Bookkeeping and Payroll WORLDs. The Tax WORLD holds its organizer Forms and tax season Drip Sequence Templates, Payroll has its own Document Generators, and nobody in Bookkeeping has to scroll past either. The managing partner sees all three from the Super WORLD.

Spin up a WORLD for each office or region, each with its own CRM Targets, assets and workflows. Head office keeps centralized oversight through the Super WORLD, or by belonging to every office’s WORLD, and every office works under the same White Label branding. When you open a new location, you add a WORLD instead of a new SuiteDash account.

For example, a recruitment firm with offices in London and Sydney gives each office its own WORLD. London keeps its candidate intake Forms and its own Document Generators, Sydney runs its own Project Generators and client list, and the head office sees both through the Super WORLD. When the firm opens in New York, it adds a third WORLD, and nothing has to move between accounts.

Staff see only what belongs to their WORLDs, which means less clutter, fewer distractions and less risk of error. Staff who belong to more than one WORLD turn each one on or off from the WORLDs list. For every WORLD you set its Default State and whether Staff may toggle it, or use Force & Hide to keep it always active and out of the list, and you can apply those settings to all existing Staff members at once.

For example, a project manager at a web design agency belongs to both the Website Builds WORLD and the SEO WORLD. On build days she switches SEO off, and her Forms, Generators and client lists show only build work. New hires start in a single WORLD, so on day one they see the handful of assets they need instead of the whole account.

WORLD-level segmentation keeps each client’s information with the Staff who should see it. A client assigned to a WORLD, along with their Projects, Deals and Documents, is hidden from anyone outside that WORLD, Staff and freelancers alike. The Add to WORLDs and Remove from WORLDs automations keep assignments current as clients come and go, and a Global WORLDs setting can hide any CRM Target that hasn’t been assigned yet.

For example, a wealth management firm puts its private clients in a Private Client WORLD that only two senior advisors belong to. Those clients’ records, Projects, Documents and Deals stay out of view for the rest of the office, and when a new private client signs, the onboarding Form assigns them to that WORLD on the way in.

As the Super Admin, you hold the Super WORLD, which sees every Contact and asset in your portal. Put each freelancer or assistant in a limited-access WORLD with only the CRM Targets, Task Templates and Forms they need. Keep your critical Automations and Generators in a WORLD they don’t belong to, or hide everything unassigned, and your helpers can’t see or change the systems your business runs on.

For example, a solo bookkeeper brings on a virtual assistant for client intake. The assistant’s WORLD holds the intake Form, the onboarding Task Templates and the new clients they work with. The bookkeeper’s invoice generators, engagement Document Generators and Auto-Templates sit in a WORLD only she belongs to, so the assistant can help without ever touching what keeps the practice running.