Setting Up Your Team

Tutorials10 min read

This tutorial is for team leaders, project managers, and administrators who need to organize a translation team in Lectio. By the end, you will have a team created, members invited, a shared glossary in place, and a workflow-driven project ready for your translators to begin work.

We will use a running example: a mission organization setting up a team to translate a multi-volume discipleship curriculum from English into two Southeast Asian languages.


Step 1: Create a Team#

During first-time setup, choose Translation and editing (recommended), With proofreading, or Suggested edits before naming your team. Customize opens the workflow editor so you can change the name, steps, order, and text access before continuing. Your choice becomes the team's default workflow for new projects; you can change it later in team settings. In the suggested-edits workflow, a Reviewer proposes changes and an Editor accepts or rejects them. When setup creates a new member's account, it also saves that person's invite-slot responsibility as a workflow default. Existing account invitations can be assigned defaults after they accept.

To create a team later:

  1. In the sidebar, click Teams
  2. Click Create Team
  3. Enter a team name — choose something that identifies the group clearly (e.g., "Southeast Asia Translation Team" or "Spanish Publishing Division")
  4. Click Create
On the Teams page, click Create Team, enter a team name, then click Create. Animation of the Your Teams page, which lists one team you own (Spanish Publishing) and one you belong to (Bible Study Network). The pointer clicks Create Team at the top of the page. A Create Team dialog opens with a Team name field, and “Youth Curriculum” is typed into it. The pointer clicks Create; the button shows a spinner, the dialog closes, and Youth Curriculum appears first under Teams You Own, marked Owner, with 1 member. The page now says 3 teams total.

Your team is now created, and you are its Owner. You can create multiple teams if your organization has separate groups working on different language pairs or projects.

Tip: If your organization works across several language pairs, consider creating one team per language pair or regional group. This keeps shared glossaries, translation memories, and project lists focused and manageable.


Step 2: Invite Members#

With your team created, invite the translators, editors, and proofreaders who will be working on your projects.

  1. Open your team from the Teams page
  2. Open the People section
  3. Under Add Member, enter the person's email address
  4. Choose their access level (see Step 3 below)
  5. Click Add member. Repeat for each person
Under Add Member on the People section, enter an email address, choose their access (most translators are Members), then click Add member. Animation of the Add Member section of a team’s People settings. The section explains that existing Lectio users get an invitation and new people get an account and a setup link. The pointer clicks the Email field and types [email protected]. Under Access level are three cards: Member (“Does the work they’re assigned”), Project manager (“Sets up projects and workflows and hands out work”) and Admin (“Runs the team: people, settings, every project”); Member starts selected, and the pointer selects Project manager. It clicks Add member; the button shows a spinner, then the form clears, Member is selected again, and a green line reads “Invite sent to [email protected]”.

What happens next depends on whether the person already uses Lectio:

  • If they already have a Lectio account, they get an invitation to accept
  • Otherwise, Lectio creates their account, adds them to the team, and emails them a setup link

Note: A setup link for a new account is valid for 7 days. If it expires, the person can still set a password with Forgot password? on the sign-in page, because their account already exists. An invitation to an existing account stays pending until they accept it; you can cancel it from the Pending Invites list in the People section.


Step 3: Understand Access Levels#

Every teammate has one of three access levels. Access controls what someone can see and change. It does not decide who translates or edits — that comes from workflow assignments in Step 5.

AccessWhat they can do
OwnerFull control over the team — billing, settings, membership, projects, and all content. There is one Owner per team
AdminRuns the team: invite and remove people, change access, manage team settings, and see every shared project
Project managerSet up projects and workflows, hand out work, and manage shared glossaries and translation memories. Sees every shared project
MemberDoes the work they're assigned. Sees only assigned documents; can translate, edit, review, and comment on them

Choosing the right access

  • Translators, editors, and proofreaders: Member. What each of them does is set per workflow step, not by their access.
  • Coordinators who create projects and assign work: Project manager
  • Operations staff who manage people and settings: Admin

You can change a member's access at any time with Edit access in the People section.

The People section lists every member with their access level. Use Edit access or Remove next to a name. The People section of the Spanish Publishing team page, headed “Members (6)” with a “How do access and assignment work?” link. Each row shows a person’s initial, name and email, and a badge with their access. Maria Santos (you) is the Owner, Grace Mwangi is an Admin, Priya Raman is a Project manager, and Daniel Okafor (usually Translation), Lucía Fernández (usually Editing) and Tomás Herrera (usually Proofreading) are Members. Every row except the owner’s has Edit access and Remove buttons.

Step 4: Create a Shared Project#

Now create a project that your team will work on together.

  1. In the sidebar, click Projects
  2. Click New project
  3. Enter a project name (e.g., "Discipleship Curriculum Vol. 1 - Khmer")
  4. Select the source and target languages
  5. Under Team, select the team you just created. This shares the project with all team members based on their roles
  6. Click Create Project
Click New project, name the project, choose the team and both languages, then click Create Project. Animation of the Projects page. A click on New project opens the New Translation Project dialog. “Discipleship Course – Spanish” is typed into Project Name. The Team list is opened and changed from Grace Fellowship to Spanish Publishing Division. Source Language already shows English; a click on Target Language opens a language list, “spa” is typed into its search box, and Spanish is chosen. The dialog then shows “English → Spanish” and the Create Project button becomes available.

The project now appears under Shared with me for every member of the team. Team members with the appropriate roles can upload documents, manage settings, and begin translating.

Tip: For multi-language projects (e.g., the same curriculum translated into Khmer, Thai, and Burmese), create a separate project for each target language. This keeps translation memories, glossaries, and workflows language-specific.


Step 5: Create a Theological Glossary#

Consistent terminology is critical when multiple translators work on the same body of content. Before your team starts translating, create a glossary of key terms.

  1. In the sidebar, click Glossaries
  2. Click Create Glossary
  3. Enter a name (e.g., "Discipleship Curriculum Theological Terms - Khmer")
  4. Select the source and target languages
  5. Click Create

Now add your key terms:

  1. Open the glossary
  2. In the empty row at the top of the term table, type the Source term (e.g., "justification"), the Preferred term — the approved translation in your target language — and an optional Context note explaining usage (e.g., "Pauline usage — God's declaration of righteousness, not the process of becoming righteous. Use this term consistently in Romans and Galatians materials.")
  3. Click Add (or press Enter). New terms start as Unconfirmed
  4. Repeat for each term
Type the source term, the preferred translation and an optional context note in the top row of the table, then click Add. Animation of a glossary page, Discipleship Curriculum Terms (English to Spanish, 4 terms, Owner). Above the term table a note says to enter the preferred dictionary or citation form, since Lectio adapts the grammar to each sentence. The table lists disciple → discípulo, grace → gracia, Holy Spirit → Espíritu Santo and justification → justificación, each marked Confirmed, with a context note. In the empty row at the top, the pointer types “covenant” as the source term, “pacto” as the preferred term and “God’s binding promise to his people” as the context, then clicks Add. The row clears and covenant → pacto appears at the top of the table marked Unconfirmed. The page now counts 5 terms, 1 needing review, and a Confirm All button appears.

Share the glossary with your project

  1. Open the project and go to its Glossaries & TM tab
  2. Under Available, click Link beside the glossary you just created. It moves to Linked
  3. The glossary is now active — the AI will use these terms when generating suggestions, and translators will see flagged terms as they work

Building an effective glossary

For a discipleship curriculum, your glossary might include terms like:

  • Core theological vocabulary (grace, redemption, sanctification, covenant, atonement)
  • Roles and titles (elder, deacon, pastor, disciple)
  • Concepts with culturally sensitive translations (fellowship, worship, prayer, communion)
  • Technical terms specific to the curriculum (any coined terms or phrases unique to the material)

Tip: Start with 30-50 essential terms before translation begins. Add more as translators encounter ambiguous or contested terms during their work. A living glossary that grows with the project is more useful than trying to be exhaustive upfront.


Step 6: Set Up a Workflow#

Workflows define the steps each document goes through before it is considered complete. This is how you ensure quality control and coordinate handoffs between team members.

  1. Open your project

  2. Open the Workflow tab. The project already has your team's default workflow, or the Solo Freelancer preset

  3. Click Edit steps

  4. Use + Add Step to add steps and the × on a step to remove one. A common setup for a curriculum translation project:

    • Pre-translation — a project manager or senior translator reviews the source document, flags difficult passages, and adds glossary terms
    • Translation — the assigned translator works through the document
    • Proofreading — a second translator or editor reviews the completed translation for accuracy, consistency, and natural expression
  5. Click Save Changes

  6. Click Manage Assignments and, under Default Assignments, use Add on each step to choose who does it

In the project’s Workflow tab, open Manage Assignments and add a default person to each step. New documents inherit those assignments. Animation of a project with Translation, Editing and Proofreading steps. The pointer opens Manage Assignments, clicks Add beside Translation, and chooses Lucía Fernández. Her name appears under Default Assignments. The pointer then opens Documents: both documents now show Lucía on Translation, with Ji-woo on Editing and Daniel on Proofreading. Defaults also apply to eligible existing documents; per-document overrides and work already underway can keep their own assignments. This example has no overrides.

How workflows operate

  • When a translator completes their step (e.g., finishes translating all segments), they mark the step as complete
  • The next person in the workflow is automatically notified that the document is ready for their review
  • The workflow advances step by step until all steps are complete
  • Project managers can see the status of every document across all workflow steps from the project's Documents tab

Note: You can customize workflows per project. A simple internal translation might need only Translation and Proofreading. A formal publication might add steps for theological review, back-translation, or final sign-off.


Step 7: Assign Documents#

For projects with multiple documents — such as a curriculum with many chapters — you can assign specific documents to specific translators.

  1. Upload all documents to the project (see Your First Translation Project for upload instructions)
  2. Open the project's Documents tab
  3. On a document, click the step you want to fill (or its amber Assign button for that step, such as Assign Editing), then choose the team member. The people who usually do that step are listed first
  4. To make that person the step's default, tick Also make them the default for Editing in this project (named for the step you are filling) before choosing. Defaults are assigned on every document that has nobody on that step, and on documents added later
Click a workflow step on a document and pick a person. The people who usually do that step are listed first. Animation of a project's Documents tab. The document “Lesson 2 – Prayer” has finished Translation, and its Editing step is waiting for someone, so the document shows an amber “Assign Editing” button. Clicking the Editing step itself opens the Editing assignment list under the document's Editing step. A search box sits at the top. Under “Usually does Editing” are “Assign me (Maria Santos)” with “Did Editing 2 weeks ago”, Ji-woo Park, a team admin, with “Default for Editing”, and Lucía Fernández with “Did Editing 3 days ago”; everyone else on the team follows below. A checkbox at the bottom reads “Also make them the default for Editing in this project”, and a link asks “How are people suggested?”. Choosing Ji-woo Park closes the list: her initial appears on the Editing step, and the document's button changes to “Waiting on Ji-woo Park”.

This is useful when:

  • Different translators have different areas of expertise (e.g., one handles the theological chapters, another handles the practical application chapters)
  • You want to distribute workload evenly across the team
  • Certain documents have higher priority and should go to your most experienced translators

What Happens Next#

With your team, project, glossary, and workflow in place, your translators can begin working:

  1. Translators see their assignments on their personal dashboard when they log in — each assignment shows the document name, workflow step, and current status
  2. They open a document and begin translating in the focused workspace, with access to the shared glossary and translation memory
  3. When they complete their step, they mark it done, and the next person in the workflow is notified automatically
  4. Project managers monitor progress from the project's Documents tab, seeing which documents are in which stage and whether anything is blocked
Each document shows its next action, how many steps it has passed, and who holds each step. A project's Documents tab as its owner sees it, with four lessons in a five-step workflow: Bible Verse Review, Pre-translation, Translation, Editing and Proofreading. Each document card shows the file name and size, a next-action button, a progress bar counting steps, and a row of step pills: green with a check for finished steps, outlined in the step's colour for the active step, and grey for steps still to come, each with the initial of the person assigned. Lesson 1 is finished and offers Export. Lesson 2 is in Proofreading and reads “Waiting on Daniel Mensah”. Lesson 3 is in Editing with nobody assigned, so it shows an amber “Assign Editing” button. Lesson 4 is at the first step and offers “Review Bible verses”.

As your team works, translation memory builds automatically. Each confirmed segment becomes a reference for future AI suggestions — across this project and any future projects that use the same language pair and translation memory. The investment you make in glossary curation and quality translation compounds over time.


Quick Reference#

TaskWhere to find it
Create a teamTeams > Create Team
Invite membersTeam page > People > Add Member
Change member rolesTeam page > People > Edit access
Create a shared projectProjects > New project > Select team
Create a glossaryGlossaries > Create Glossary
Link glossary to projectProject > Glossaries & TM tab > Link
Set up a workflowProject > Workflow tab > Edit steps
Assign documentsProject > Documents tab > click a step on the document

Need more help?

Chat with our AI assistant or create a support ticket.