Clear roles. Two people on every critical step.

IFAASTasdiq separates who submits a document, who reviews it and who approves the result, following the maker-checker controls banks already use.

Three teams, eight roles

  • Your institution: Client user · Organisation admin · Organisation approver
  • Expert reviewers: Junior auditor · Senior auditor
  • IFAAS platform team: Super admin · System approver · Platform owner

How a review changes hands

  1. Your institutionSubmit

    Upload and redact your document, then choose references.

  2. IFAASTasdiq platformRoute

    Match the request to expertise, seniority and workload.

  3. Junior auditorFirst pass

    Run the analysis, then check and edit the findings.

  4. Senior auditorSecond review

    Approve the findings or record the reason for any override.

  5. IFAASTasdiq platformRelease

    Send the report and audit trail to the client.

  6. Your institutionReceive

    Download the report and message the auditor.

The review passes from the client to the platform, then to two auditors in turn. Nothing returns to the client until the senior auditor approves it.

Your institution

Client user

Who: compliance officers, legal counsel, product managers and Shariah department staff who need documents reviewed.

  • Upload documents and choose the review type and jurisdiction
  • Choose the references to check against, and redact sensitive details if they wish
  • Track progress, message the assigned auditor, and download the findings and report

Control: the account works only after the organisation approver activates it.

Organisation admin

Who: the person who runs IFAASTasdiq for the institution, often in Shariah compliance, compliance operations or IT.

  • Create and manage user accounts and permissions
  • Upload the institution's own references, public or private
  • Manage settings, branding and payment preferences
  • Monitor requests, usage and the institution's audit trail

Control: new users and payment changes take effect only after the organisation approver signs off.

Organisation approver

Who: a second person at the institution, separate from the admin, such as a compliance manager or information-security officer.

  • Approve or reject each new user account before it is activated
  • Approve or reject any change to the payment method
  • Have each decision recorded

Why it matters: no single person can give access to the institution's documents or change how it pays.

Expert reviewers

Reviews are carried out by Shariah and regulatory auditors onboarded and vetted by IFAAS. Each auditor is tagged by expertise and seniority, and passes identity and background checks before seeing any document.

Junior auditor

Who: a qualified Shariah or regulatory auditor matched to the document's subject and jurisdiction.

  • Take a review from the queue or the review pool, or return one outside their expertise for re-assignment
  • Check the document's sensitivity, scope and references
  • Set up the approved review templates, run the analysis, and check every finding, citation and amendment
  • Submit the assessment for senior review

Senior auditor

Who: an experienced Shariah or regulatory auditor with the authority to sign off.

  • Review the assessment, the reference selection and the evidence
  • Ask for further work or a targeted re-run where needed
  • Amend findings, recording the reason for any material override
  • Validate the final report for release to the client

Control: every override and its reason stays in the audit trail.

IFAAS platform team

IFAAS runs the platform with the same separation of duties it asks of its clients.

  • Super admin. Onboards institutions, creates auditor accounts with expertise tags, manages usage limits, library content and review templates, monitors queues and approves transfer requests.
  • System approver. An independent checker who reviews every super admin and auditor account request, carries out identity and professional checks, and records each decision.
  • Platform owner. The top-level account holder, who creates, edits and deactivates super admin accounts and monitors administrative access.
More detail
  • Access to client data at IFAAS follows approved permissions. The system approver acts independently of whoever created the account being approved.

Who creates, who approves

ActionDone byApproved by
New client user accountOrganisation adminOrganisation approver
Change of payment methodOrganisation adminOrganisation approver
New auditor accountSuper admin, setting expertise and senioritySystem approver, after identity and background checks
New super admin accountPlatform ownerSystem approver
Private reference, such as a Shariah board resolutionOrganisation adminThe assigned auditor, for that institution only
Public reference, such as a law or circularOrganisation adminAn IFAAS library administrator, before it joins the shared library
Transfer of a review to another auditorAuditor, giving a reasonSuper admin
Review findingsJunior auditorSenior auditor
Override of a findingSenior auditorA written reason, kept in the audit trail

Walls that stay up

  • No institution can see another institution's documents, references or results.
  • No one at IFAAS sees client data beyond what their approved permissions allow.
  • No client user, auditor or super admin account becomes active without a second person's approval.
  • No report is released until a senior auditor has approved it.

See how the roles map to your approval policy