IT & admin

Make day one an install and a sign-in

“A new hire spends their first week setting up tools instead of doing the job.”

Everything the role needs travels in one bundle: the persona, its boards, its scheduled workflows, its sample data and its connectors, delivered to the people entitled to it and locked against editing.

1. 1

   Build the role once

   One persona per job. It carries the prompt, the skills, the agents and the connectors that job needs.

   Try this

   Copy

   Build a persona for the <role> job: the prompt, the skills, the agents and the connectors that job needs. List what you included and what you deliberately left out.

   Personas→

   1:50

2. 2

   Give it the board it works from

   Boards travel inside the bundle and arrive seeded, not empty.

   Dashboards→

   1:10

3. 3

   Ship the standing jobs switched off

   Scheduled and polled workflows arrive with the persona and land disabled, so a new machine does not start sending on its first morning.

   Try this

   Copy

   Add the standing jobs to that persona, and make sure they arrive disabled so a new machine does not start sending on its first morning.

   Dynamic Workflows→

   1:35

4. 4

   Include sample data in the real format

   A bundled dataset seeds into Data Sources on install. Swap in a real export and every workflow keeps working, because the columns match.

   Data Sources→

   0:11

5. 5

   Deliver it to the right people only

   A protected marketplace is fetched by the server, not the client. The access token never reaches a laptop, content is sealed per marketplace, and revoking someone takes effect within fifteen minutes.

   Unified Marketplace→

   

6. 6

   Move a whole setup between machines

   When someone changes laptop, one encrypted file carries their personas, connectors, workflows, boards and chats across.

   Move to Another Machine→