Yurbi Multi-Tenant App Shield Configuration (Onboarding)

Yurbi Multi-Tenant App Shield Configuration (Onboarding)

1. 01

   Confirm the client database is on a supported engine before install

   Yurbi connects to SQL Server, PostgreSQL, MySQL, Oracle, or ODBC through read-only connections. Log the engine, schema, and a read-only service account in the client onboarding record so the deployment step does not stall on credentials.

2. 02

   Install Yurbi on the client's own infrastructure and register the production license

   Yurbi is self-hosted only, so the agency owns deployment. The Starter plan at $833.33 monthly (billed annually) covers 1 dev plus 1 production license and up to 75 named users; Growth at $1500 monthly raises the ceiling to 250 named users. Match the license tier to the client's named-user count before provisioning.

3. 03

   Create the database connection in the Yurbi admin panel

   Point Yurbi at the client's database using the read-only account. Verify the connection returns rows before moving to security rules, since App Shield policies attach to a live connection.

4. 04

   Define App Shield tenant isolation rules at the query layer

   Map each tenant identifier to the client's user or account column so every query is filtered before results return. App Shield enforces isolation at query time rather than in the presentation layer, which is the control auditors will ask about.

5. 05

   Test isolation with two synthetic tenant logins

   Sign in as tenant A and tenant B and confirm neither can surface the other's rows in an ad-hoc report. Record the test date and result in the client's delivery file; this is the evidence an agency needs if a client disputes a data leak.

6. 06

   Apply white-label branding so the client's product UI carries no Yurbi marks

   Replace logos, colors, and naming in the Yurbi branding settings, then load the embedded views inside the client product to confirm the chrome matches. Branding gaps are the most common reason a client rejects an embedded analytics handoff.

7. 07

   Build the first dashboard templates against the client's core product metrics

   Ship 5 pre-built dashboard templates mapped to the metrics the client already reports on. The no-code drag-and-drop report builder lets the client's end users extend these without SQL, which reduces the agency's change-request load.

8. 08

   Schedule automated report delivery and set a query performance review

   Configure scheduled report delivery for the client's stakeholders and cache frequently hit datasets in-memory. Book a 30-day review of query times against the retainer scope so slow tenants get tuned before renewal conversations.