Shared knowledge without losing control.
In an organisation, several people may need to answer questionnaires using the same approved organisational knowledge.
RepliSec Teams is designed to let them collaborate without giving everyone unrestricted access to every customer engagement.
RepliSec Teams is planned, not built. Everything on this page describes intended capability. RepliSec itself, the single-user product, is available today as an invite-only alpha.
One organisation. Many engagements. Controlled access.
Shared organisation knowledge can be made available across the organisation, while customer-specific work is assigned, shared or restricted according to role and responsibility.
- Shared organisation knowledge
-
Customer A
- Owner
- Contributors
- Reviewers
-
Customer B
- Owner
- Contributors
-
Customer C
- Owner
- Read-only users
Each customer engagement is an organisation-owned object with configurable access, rather than something tied permanently to the person who created it. People join and leave; the engagement and its history stay with the organisation.
The knowledge model does not change. Foundation, organisation and customer-specific knowledge work exactly as they do in RepliSec. Teams governs who can see and change each part of it.
Tier 2 becomes shared
In RepliSec, organisation knowledge belongs to one practitioner. In RepliSec Teams, that same tier becomes a shared organisational knowledge base available to authorised users: one approved answer, reused by everyone entitled to it.
What RepliSec Teams adds.
The core questionnaire and knowledge capabilities stay consistent. Teams adds the identity, access and governance required for people to work together securely.
Multi-user collaboration
Multiple users within one organisation, working the same questionnaires from the same trusted knowledge rather than from private copies.
Shared organisational knowledge
Tier 2 knowledge and the approved-answer library become organisation-wide assets, so an approved answer is written once and reused everywhere it applies.
Customer engagement ownership
Each engagement has a configurable owner, with contributors and reviewers assigned per customer rather than granted blanket access to everything.
Role-based access control
Contributor, reviewer and administrator roles determine who can manage shared knowledge, contribute to engagements, approve responses and reach sensitive evidence.
Review and approval workflows
Responses can move through a defined review step before they leave the organisation, so approval is a recorded event rather than an informal one.
Organisation-wide audit history
Who changed what, when, and which answer was approved by whom, across every engagement rather than just an individual's own activity.
Organisational identity integration
Access through the organisation's existing identity provider, using familiar, centrally managed credentials and standards-based authentication.
Single sign-on
Users sign in with the account they already have, and leavers lose access when that account is disabled.
Centralised administration
Organisation-level administration of users, roles, shared knowledge and engagement access, in one place.
Designed for organisational identity and access.
RepliSec Teams is planned to integrate with an organisation's existing identity provider, allowing users to access the platform through familiar, centrally managed credentials.
Role-based access controls will determine who can administer the organisation, manage shared knowledge, contribute to customer engagements, review responses and access sensitive evidence.
- Organisational identity integration
- Single sign-on
- Standards-based authentication
- Role-based access control
- Centralised user administration
One knowledge model. Two ways of working.
The difference is not the number of customers, or whether customer-specific knowledge is available. It is multiple users, shared knowledge, identity, access control and workflow governance.
| Capability | RepliSec | RepliSec Teams |
|---|---|---|
| Intended for | Individual practitioners | Organisational teams |
| Users | One | Multiple |
| Multiple customers | Yes | Yes |
| Three-tier knowledge model | Yes | Yes |
| Customer-specific knowledge | Yes | Yes |
| Approved-answer library | Yes | Shared |
| Local or self-hosted deployment | Yes | Yes |
| Shared organisational knowledge | Not applicable | Yes |
| Customer engagement ownership | Individual | Configurable |
| Review and approval workflows | No | Yes |
| Role-based access control | No | Yes |
| Organisational identity integration | No | Yes |
| Audit history | Individual activity | Organisation-wide |
Start individually. Collaborate when your organisation is ready.
RepliSec gives individual security professionals a complete workspace for managing trusted answers, customer knowledge and security questionnaires. It is source available under the Functional Source License and available now as an invite-only alpha.
RepliSec Teams will extend that same model with shared organisational knowledge, secure multi-user access, review workflows and team administration. It is not yet built.
RepliSec Teams will be a commercial product. The single-practitioner RepliSec remains complete and free; Teams adds the identity, access control and governance an organisation needs, and is what funds continued development of both.
If collaborative deployment matters to your organisation, register your interest. It directly shapes what gets built first.