Setting Up Your Team
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:
- In the sidebar, click Teams
- Click Create Team
- Enter a team name — choose something that identifies the group clearly (e.g., "Southeast Asia Translation Team" or "Spanish Publishing Division")
- Click Create
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.
- Open your team from the Teams page
- Open the People section
- Under Add Member, enter the person's email address
- Choose their access level (see Step 3 below)
- Click Add member. Repeat for each person
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.
| Access | What they can do |
|---|---|
| Owner | Full control over the team — billing, settings, membership, projects, and all content. There is one Owner per team |
| Admin | Runs the team: invite and remove people, change access, manage team settings, and see every shared project |
| Project manager | Set up projects and workflows, hand out work, and manage shared glossaries and translation memories. Sees every shared project |
| Member | Does 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.
Step 4: Create a Shared Project#
Now create a project that your team will work on together.
- In the sidebar, click Projects
- Click New project
- Enter a project name (e.g., "Discipleship Curriculum Vol. 1 - Khmer")
- Select the source and target languages
- Under Team, select the team you just created. This shares the project with all team members based on their roles
- Click Create Project
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.
- In the sidebar, click Glossaries
- Click Create Glossary
- Enter a name (e.g., "Discipleship Curriculum Theological Terms - Khmer")
- Select the source and target languages
- Click Create
Now add your key terms:
- Open the glossary
- 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.")
- Click Add (or press Enter). New terms start as Unconfirmed
- Repeat for each term
Share the glossary with your project
- Open the project and go to its Glossaries & TM tab
- Under Available, click Link beside the glossary you just created. It moves to Linked
- 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.
-
Open your project
-
Open the Workflow tab. The project already has your team's default workflow, or the Solo Freelancer preset
-
Click Edit steps
-
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
-
Click Save Changes
-
Click Manage Assignments and, under Default Assignments, use Add on each step to choose who does it
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.
- Upload all documents to the project (see Your First Translation Project for upload instructions)
- Open the project's Documents tab
- 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
- 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
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:
- Translators see their assignments on their personal dashboard when they log in — each assignment shows the document name, workflow step, and current status
- They open a document and begin translating in the focused workspace, with access to the shared glossary and translation memory
- When they complete their step, they mark it done, and the next person in the workflow is notified automatically
- Project managers monitor progress from the project's Documents tab, seeing which documents are in which stage and whether anything is blocked
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#
| Task | Where to find it |
|---|---|
| Create a team | Teams > Create Team |
| Invite members | Team page > People > Add Member |
| Change member roles | Team page > People > Edit access |
| Create a shared project | Projects > New project > Select team |
| Create a glossary | Glossaries > Create Glossary |
| Link glossary to project | Project > Glossaries & TM tab > Link |
| Set up a workflow | Project > Workflow tab > Edit steps |
| Assign documents | Project > Documents tab > click a step on the document |