Rolling out to a team and scope levels
2 min read
Rolling out to a team
Once the space is ready, each relationship manager / financial advisor installs Remy for themselves with one button. Rolling out to a team is about deciding who is in, what they can see, and in which order they go.
Decision | How it is set |
|---|---|
Pilot group | A named set of relationship managers / financial advisors and their clients, agreed before the design phase. Private clients only in the first wave is a common choice. |
Who is a user's client | The CRM is the authoritative list, complemented by mailbox correspondents and the document folders the user can see. Configured once per deployment. |
Teams and deputies | Groups synchronised from the bank's identity provider - desk, segment, region, deputy pool. Team membership is never maintained inside Remy. |
Order of installation | One user at a time for the first few, then the rest. The first run per user mines their whole book; stagger large books outside working hours. |
Handover | When a relationship moves, the successor's next run rebuilds their second brain from the same client memories. Nothing to migrate. |
Scope levels
Everything Remy delivers - memories, registers, prepared letters, dashboard state, skills and configuration - is governed by one three-level scope model. Groups come from the IdP; a skill can never widen what its caller is entitled to see.
Per User: The relationship manager's / financial advisor's own working memory, notes and drafts. Private by default. Personal skill variants with no effect on anyone else.
Per Team: A shared memory of a jointly covered relationship, visible to the desk and to deputies during cover. Team-tuned cadence, thresholds, templates, language, segment logic.
Per Organisation: The governed, promoted memory - compliance, mandate, commitments, matters in flight, change log. Bank-standard skills: house view, compliance monitors, corporate identity, the mandatory write policy.
Promotion - what moves from a user's memory to team or organisation folders, by whom and under which rule, is agreed in the design phase, held in the description file and folder permissions, and recorded in the change log. Promotion is policy, not agent discretion. Personal relationship detail stays within the user's scope.
Precedence - user overrides team overrides organisation, except for what the bank locks at organisation level: typically compliance monitors, retention classes and the excluded categories.
More than one memory per client - the same client can legitimately hold a user memory, a team memory and an organisation memory, built from the same sources with different configuration. Same contracts, same provenance, same audit trail.
Organisation view - the same aggregation Remy does for one user, run over the shared folders for team leads, deputies and compliance: coverage, handover, open commitments across the book.
Team and organisation scope require IdP group synchronisation. Until federation is in place, Remy runs at user scope; the client document folders are shared from the start regardless.