Applications

Applications answer who uses what. Torque has one Investor experience, an Issuer workspace, an administration workspace, and an Operator enterprise scope. Operator is a business role, not a separate Torque application. The Platform operating model defines the roles used throughout the product.

Application map

Application or scope	Role	Main work	Inputs	Outcome and handoff
One Torque investor experience	Investor	Discover funds, complete eligibility, subscribe, fund, view holdings, receive distributions, and redeem.	Public fund information, owned profile, eligibility evidence, terms, and funding choice.	A holding or an actionable recovery state. Handoff goes to Issuer or Administrator for owned operations.
Issuer workspace	Issuer	Create, configure, launch, value, service, distribute for, redeem, and close funds.	Fund terms, disclosures, documents, operating data, holding inventory, and approvals.	A serviced fund and confirmed records available to Investors. Handoff goes to Administrator for all-fund administration, oversight, or exceptions.
Administration workspace	Administrator	Access ALL funds and ALL issuers. Administer users, permissions, settings, records, and exceptions through all admin-web functionality.	Organization context, operational records, provider state, and exception evidence.	A governed platform decision, oversight record, or recovery handoff.
Operator enterprise scope	Operator	Operate the partner's OWN Torque-based platform within enterprise-agreement scope.	Enterprise agreement, platform scope, and operating responsibilities.	Partner operation within its own scope. No separate Torque application or permission model.

Choose by question

• A Prospect starts with Platform capabilities.
• An Issuer starts with the Issuer workspace and Launch a fund.
• An Investor starts with the one Investor experience and Onboard an Investor.
• An Administrator starts with the administration workspace and Cancel, recover, and hand off work.
• An Operator starts with enterprise scope, not a new application.
• A compliance reviewer starts with Compliance.
• An integration team starts with Reference.

Handoffs

An application presents a user task. Its owning service records the resulting decision or side effect. The receiving role continues only when the required record or notification exists.

Handoff	Sending role	Receiving role	Evidence to continue
Fund readiness to publication	Issuer	Issuer approval process and Administrator when an exception crosses scope	Terms, disclosures, readiness result, and approval record
Investor eligibility to subscription	Investor	Investor experience and Issuer operations	Profile status, eligibility decision, accepted terms, and signed documents
Subscription to servicing	Investor	Issuer	Authoritative completed funding result, Issuer acceptance, fulfillment result, confirmed holding record, and confirmation
Issuer servicing to Investor	Issuer	Investor	Confirmed holding, distribution result, or confirmed redemption proceeds receipt
Provider failure to recovery	Any active role	Administrator and the owning service	Identifiable state, error context, and audit record
Partner operation to platform owner	Operator	Enterprise agreement owner	Scope, contract, and escalation path