How Data Clan’s Identity and Trust services fit together.
Start with the relationship
A portal, a private service connection and a partner scheme need different kinds of confidence. Decide what each person, application or organization needs to do and what evidence justifies it.
dc:id: identity and access
Connect configured account providers and managed application identities. Use native sign-in and organizational administration for your business context. The receiving application validates identity information and enforces its resource permissions.
dc:pki: private certificate trust
Manage private authorities, issuance policies and revocation. Establish the required trust anchors in relying systems and plan installation, renewal, key custody and revocation checks.
dc:trust: scheme governance and assurance
Define versioned scheme rules and participant roles. Record agreements, evidence and assessment, with independent approval and current accreditation status.
Connect the responsibilities explicitly
A signed-in account or valid certificate is not an assurance assessment. Integrate member workflows and scoped dc:trust decisions with the services that rely on them. Each service retains its own permissions and data boundary.
Start with one useful implementation
Prove a representative permitted action and a relevant denied or unapproved case, then agree the operating handover. Plan your next step.