Identity and permissions
Sign in through OAuth/OIDC-based authentication, with identity settings agreed for your deployment. Use permission groups to separate viewing, creating, and changing records, including ledger viewing and posting.
Understand who can access your data, how activity is recorded, and how your service is supported. Review Finsaku’s controls and deployment arrangements against your operational requirements.
A closer look
Sign in through OAuth/OIDC-based authentication, with identity settings agreed for your deployment. Use permission groups to separate viewing, creating, and changing records, including ledger viewing and posting.
Review recorded changes and their context. Follow the outcome of automated workflows, including actions that failed at a connected provider.
The documented standard deployment uses AWS in the Ireland region, with encrypted file storage and a database that is not publicly accessible. Confirm processing locations for your deployment and connected providers.
The standard hosted deployment includes database and file-storage backup mechanisms. Backup retention, restoration procedures, and recovery objectives are defined in the applicable service documentation.
Agree support channels, incident contacts, response terms, and availability commitments as part of your service agreement. Ask our team for the deployment evidence needed for your assessment.
Connected agents work within the signed-in user’s permissions. Set access around customer records, applications, documents, and configuration tasks to match each role’s responsibilities.
Privacy and resilience
Bring your data protection and operational resilience requirements into the conversation early.
Use granular permissions and recorded activity to support your data protection processes. Clarify data processing roles, terms, providers, retention, and how requests about personal data are handled.
GDPR guidanceWhere DORA applies to your organisation, review Finsaku as part of your technology service assessment. Discuss incident coordination, recovery arrangements, service commitments, third-party dependencies, and the evidence needed for continuity and exit planning.
DORA guidanceCompliance also depends on your policies, configuration, contracts, and day-to-day operations. Confirm responsibilities and service commitments for your deployment.
Discuss your requirementsLet’s talk
Discuss access controls, hosting, recovery, and service responsibilities with the team behind your deployment.