01Available
Signature requests with templates
Signature requests with templates is handled inside the Sign record model with ownership, permission checks and a traceable state history.
Documents & approval
Sign
Run Sign work in one governed workspace.
Run signature requests with templates, parties, ordered approval, verification and immutable evidence packs.
This application uses the shared İş Zamanı identity, permission and audit contracts. Acceptance conditions for provider- or regulation-dependent capabilities are stated separately on its detail page.
sign operating scopeSample view
Sample view
Sign operating scope
01
Record
Signature requests with templates
02
Workflow
Parties
03
Control
Ordered approval
Contains no real customer data; generated to represent the application scope.
- Record
- Signature requests with templates
- Workflow
- Parties
- Control
- Ordered approval
What it does
Sign coverage
Listed capabilities follow the managed catalogue status and the plan, provider and acceptance conditions confirmed during activation.
02Available
Parties
Parties is handled inside the Sign record model with ownership, permission checks and a traceable state history.
03Available
Ordered approval
Ordered approval is handled inside the Sign record model with ownership, permission checks and a traceable state history.
04Available
Verification
Verification is handled inside the Sign record model with ownership, permission checks and a traceable state history.
Workflow
Sign operating scope
- 01
Prepare the operating context
Define ownership, permissions and the records needed for signature requests with templates and parties.
- 02
Run the work and decisions
Run signature requests with templates, parties, ordered approval, verification and immutable evidence packs.
- 03
Verify the outcome
Who approved which version and when becomes verifiable. Exceptions, approvals and resulting activities remain available for reporting and audit.
Who is it for?
Who is it for?
For teams that want to run daily work in one shared record system.
Documents & approval teams
Run signature requests with templates, parties, ordered approval, verification and immutable evidence packs. The application keeps day-to-day records in the same governed context.
Team and process leaders
Who approved which version and when becomes verifiable. Managers can review ownership, progress and exceptions without rebuilding the story from separate files.
Frequently asked questions
Frequently asked questions
What does Sign cover?
Its published scope covers Signature requests with templates, Parties, Ordered approval, Verification and Immutable evidence packs. The exact limits and provider-dependent conditions are confirmed during activation.
Does it work with the other İş Zamanı applications?
Yes. It uses shared identity, permissions, activities, notifications, documents and audit contracts; record links are enabled where the business workflow requires them.
Sign
See Sign with your own workflow.
Share the roles, records, volume and connections in your target scenario; we will confirm the activation scope and acceptance steps together.