API documentation

Enterprise onboarding

How a bank team gets a working Stonewake workspace, on one page. Every step is arranged with your named contacts, and nothing requires a change to your own infrastructure.

Workspace and teams

  • Your institution receives its own workspace: an isolated tenant with its own users, teams, audit trail, and cover-page branding on downloaded documents.
  • Teams mirror your desks. Each team's module set is trimmed to what that desk needs, and the trim applies everywhere: the dashboard navigation, downloads, and the built-in guide describe only what the team actually has.

Users and roles

  • Users are provisioned by arrangement with your administrator and hold one of four roles: viewer, analyst, compliance, or admin. Access is least privilege by default.
  • Sign-in is with work email and password, or a one-time sign-in link sent to the work email. Single sign-on (SAML 2.0, Microsoft Entra ID) is prepared and is enabled per customer once federation with your identity provider is set up; once on, joiners and leavers follow your directory, with sign-in just in time and data access still granted explicitly by a named administrator.
  • Password resets and account removals are handled administratively on request, through your named contact.

First session and support

  • The dashboard carries a built-in guide, and every user can download a quick start PDF tailored to their team's module set.
  • During an evaluation the rule is: enter no bank data. The platform researches public sources; keep your inputs to public information too: no confidential information, client data, or personal data beyond your own account details goes in.
  • Report an issue in the dashboard sidebar sends a note straight to the team with the page attached; every report is persisted on our side before delivery, so none is lost. We reply the same day.
  • Everything else: contact@stonewake.ai.

Related: Security overview, Data handling.