Skip to main content

Shared platform

Studio

Available

Run Studio work in one governed workspace.

Configure fields, views, forms, rules and simple automations through controlled, versioned changes.

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.

Request a demoPricing approach
studio operating scopeSample view
Record
Fields
Workflow
Views
Control
Forms

What it does

Studio coverage

Listed capabilities follow the managed catalogue status and the plan, provider and acceptance conditions confirmed during activation.

01Available

Fields

Fields is handled inside the Studio record model with ownership, permission checks and a traceable state history.

02Available

Views

Views is handled inside the Studio record model with ownership, permission checks and a traceable state history.

03Available

Forms

Forms is handled inside the Studio record model with ownership, permission checks and a traceable state history.

04Available

Rules and simple automations through controlled

Rules and simple automations through controlled is handled inside the Studio record model with ownership, permission checks and a traceable state history.

Workflow

Studio operating scope

  1. 01

    Prepare the operating context

    Define ownership, permissions and the records needed for fields and views.

  2. 02

    Run the work and decisions

    Configure fields, views, forms, rules and simple automations through controlled, versioned changes.

  3. 03

    Verify the outcome

    Low-code changes are governed through tenant boundaries, versions and rollback records. 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.

Shared platform teams

Configure fields, views, forms, rules and simple automations through controlled, versioned changes. The application keeps day-to-day records in the same governed context.

Team and process leaders

Low-code changes are governed through tenant boundaries, versions and rollback records. Managers can review ownership, progress and exceptions without rebuilding the story from separate files.

Frequently asked questions

Frequently asked questions

What does Studio cover?

Its published scope covers Fields, Views, Forms, Rules and simple automations through controlled and Versioned changes. 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.

Studio

See Studio 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.

Request a demo