Installing Remy in a space
2 min read
Installing Remy in a space is what makes the one-button install available to each relationship manager / financial advisor in the team. It is done once per space by an administrator, with the delivery team during the design phase.
Applies after contracting. The skill package and the administration tool are delivered with the engagement; the connectors, model and IdP federation are provisioned by IT - see Before you begin.
Checklist
# | Step | Detail | Who |
|---|---|---|---|
1 | Create the space | One agent space for the relationship-manager / financial-advisor team. Remy is installed per space; a bank with several desks may run one space per desk or one shared space with team scopes. | Administrator |
2 | Set the model | A frontier model with tool use and subagent support. Mining runs subagents per client; without subagent support it falls back to mining inline, more slowly. | IT |
3 | Connect the sources | Outlook mail and calendar as the minimum; Teams; CRM; portfolio; web search; further MCP servers as approved. Each with delegated, on-behalf-of permissions so every run executes as the invoking user. | IT · Security |
4 | Enable scheduled tasks | Required for the overnight pipeline. Each user's schedule is installed by their own first run. | IT |
5 | Publish the skills | With the administration tool, push the Remy skill tree to the space's skills folder in the knowledge base, or mount it from the platform image; when to use which route is on Architecture and data flow. Point the space's Skills tool at that folder. | Administrator (with delivery team) |
6 | Point the side panel | Set the side panel to the per-user dashboard path with the shipped installer as fallback. One setting; resolved per reader: an uninstalled user sees the installer, everyone else their own dashboard. | Administrator |
7 | Place the configuration | The description file (memory shape, exclusions) and the policy files (monitors, letters), as decided in the design phase. See Configuring the memory and tuning the monitors. | Administrator · Compliance |
8 | Create the client document folders | The organisation-level folder per client - one shared folder, subfolders for identity, residence and tax, wealth and suitability, entities, mandate, correspondence - under the bank's existing permissions. This is where documents live, once. | Administrator |
9 | Verify | Run the check skill from chat: it reports whether skills are mounted, connectors reachable, scheduled tasks enabled and the side panel resolving. Run the demo skill for a fixture-based walk-through before any real user installs. | Administrator |
10 | Invite the pilot group | Each relationship manager / financial advisor opens the side panel and presses Start installation. See Rolling out to a team. | Administrator |
What is limited without a connector
Remy installs and runs on the knowledge base alone. Each connector adds a capability; none is a hard dependency except mail and calendar for a useful daily loop. The full dependency table is on Before you begin. The check skill and every mining report state which sources were used, so nothing is assumed.