How to Connect Sastra Project Management

How-to Guides7 min read

Connect a Lectio team to Sastra to keep translation progress with the publishing schedule. Lectio remains the place for translation, review, and document assignments. Sastra manages publishing dates, downstream tasks, budgets, rights, and project completion.

This connection is available for active, paid Sastra Cloud workspaces and deployments explicitly managed and approved by the Sastra operator. Other self-hosted instances, trials, and inactive Cloud subscriptions cannot connect. Lectio checks eligibility when connecting and during ongoing sync. If verification is unavailable, sync waits while your existing work stays saved.

Use Sastra 0.5.1 or later. Lectio verifies the setup request directly with that Sastra instance, including its current administrator approval. If verification fails, restart from Sastra Settings or ask its administrator to update Sastra.

Approve a connection#

  1. In Sastra, an administrator enables Lectio in Settings → Modules.
  2. Open Settings → Lectio, enter this Lectio app's address, and continue.
  3. Sign in to Lectio as the team's owner or administrator.
  4. Check the displayed Sastra workspace and address, select the team, and approve.
  5. Return to Sastra to link an existing project or review connected project defaults.

A Lectio team connects to one Sastra workspace. Other teams and unlinked projects keep their existing behavior. Only projects shared with the connected team are eligible. The team is never selected automatically. Check its name, team ID, and owner before approving; a team that already has a connection cannot be taken over by another connection. If setup was interrupted, an administrator can cancel the pending connection in team settings. Approval and connection changes require an online connection and are never queued offline. The integration supports DOCX, ODT, and IDML translation projects; keep subtitle and video work in separate projects.

Use shared sign-in#

The server administrator must enable SASTRA_SHARED_SIGN_IN_ENABLED=true before an administrator can enable shared sign-in for a connected team in Sastra's Settings → Lectio. Each person then opens Settings → Profile → Link Lectio in Sastra and approves the link while signed in to both existing accounts.

Shared sign-in never creates an account, adds a seat, or matches accounts by email. Email addresses can differ. Sastra shows both accounts for review before saving the link. Confirm that both are yours, or cancel and switch the Lectio account. Normal Sastra login stays available. Removing team membership or revoking the connection ends sessions created through shared sign-in, while independent login continues to work.

Set project defaults once#

In Sastra's connection settings, an administrator maps your team workflow to a Sastra project template and chooses the next publishing stage and file-delivery preference. Existing projects retain their saved mappings when these defaults change.

Open Teams → your team → Security → Sastra project management to allow Sastra project managers to create projects using that workflow. Creation uses current Lectio plan limits and does not add members or buy seats.

The connected team's owner owns new Lectio projects created from Sastra. That owner's plan and file-space limits apply. Existing projects keep their owners. Only resources explicitly shared with that team are attached automatically. The owner's personal and other-team glossaries and memories stay private. Use Review connection approval to approve responsibility with a current team administrator account. This keeps project links and records the change in Connection history. A changed team owner turns off project creation until it is reviewed and enabled again.

Both administrators must approve creation from the reviewed defaults before a separate counterpart can be created. In New project, Connected to Sastra defaults on when the selected team is linked. Sastra's New project form offers the same control for Lectio. Turn it off to keep the new project separate.

Before creating a connected project, a dialog checks existing projects. Compare titles, languages, and project IDs. Choose an existing counterpart, or explicitly choose Create a separate project if none is right. No match is selected automatically. Cancel preserves your draft and creates nothing. An existing choice creates only the native project, then opens workflow mapping in Sastra. A separate choice uses the approved defaults.

Connect an existing project#

Existing projects start not connected, even when their team is linked. On the project, turn on Connected to Sastra (or Connected to Lectio in Sastra's Translation tab). The same review dialog offers authorized existing projects and a separate-project choice. Selecting a match changes no owner and grants no membership. A verified Profile account link and current project-management permission in Sastra are needed to check matches from Lectio.

Finish workflow mapping in Sastra before synchronization starts. Connecting to a newly created counterpart also waits for this review so an existing workflow is preserved. Document imports and AI-created Sastra plans remain separate until reviewed from Translation.

Turn the control off and confirm Disconnect project to stop sync in both apps. Projects, documents, translations, dates, and history stay saved. Reconnecting reviews the original pair and reuses its history. Wait and retry if disconnection is still being delivered. Cancelling unfinished creation cannot later create a duplicate counterpart.

Work on connected projects#

Continue translating and reviewing in Lectio. Root documents appear as Sastra units; split parts contribute to their root document's progress. Completing one part does not complete its siblings. Changes made offline synchronize after Lectio receives them.

The project page links to Sastra and displays the project deadline with its timezone. Sastra task deadlines remain separate from translation completion. Integration delays do not prevent you from continuing translation work.

Set the translation schedule

On the linked project's Documents tab, select Edit schedule under Translation schedule. Set the project start date, project deadline, and linked translation-task deadlines. Use Save schedule to save them in Sastra. An empty field removes its date. Calendar dates use the Sastra workspace timezone; grouped workflow steps share one deadline.

You need workflow-management permission in Lectio, a verified account link from Sastra Profile, and project-management permission in Sastra. An administrator's teammate match alone cannot delegate your authority. Matching never grants a role.

Saving shows progress until Sastra confirms the dates. If another person changes the schedule or task mapping first, your save stops and retains your entered dates. Select Reload schedule, review the current values, and enter your changes again. A temporary network error keeps the form available for retry. Scheduling is unavailable offline.

If the administrators enabled file delivery, the completed document is exported after its full workflow finishes. DOCX and ODT keep their formats. IDML delivers a portable DOCX translation; native IDML export remains available in Lectio. Sastra preserves older revisions and attaches the new file to its publishing work.

Reopening translation does not automatically reopen a completed Sastra task. The project manager reviews the downstream consequences. Neither application's project completion, financial records, or credit-spending decisions are changed by a progress update.

Pause or disconnect#

Team owners and administrators can pause or disconnect under the team's Security settings. Resume in the app where synchronization was paused. Disconnecting stops new sync work and preserves projects, translations, files, and history in both apps. If the other app is offline, the disconnect message retries automatically.

Deleting a connected team also records a disconnect message before its connection is retired. Reconnecting requires fresh administrator approval in both apps.

Source files and assignment requests#

A Sastra project manager can share a selected DOCX, ODT, or IDML attachment up to 50 MB. Lectio checks the file, permissions, and the project owner's storage and file-type limits before importing it into the connected project. Imported files wait for you to start preparation, so importing does not automatically spend preparation credits. The project shows import progress and any recovery issue. An expired grant can be renewed by sharing the same file again from Sastra.

Matched project managers can also request assignments from Sastra. An authorized teammate is assigned automatically when the step is unstarted and the workflow has not changed. Existing workers, started work, split documents, and stale requests stay unchanged and appear under Requests from Sastra. Review the normal document assignments, then use Mark reviewed to acknowledge the item. Matching accounts does not grant team membership or management privileges.

Need more help?

Chat with our AI assistant or create a support ticket.