Collaboration is essential for global scale, but data security is paramount. MultiLipi's Team Workspace allows you to provision access to translators, developers, and project managers without sharing sensitive login credentials. You can assign granular permissions, ensuring team members interact only with the specific projects and tools required for their role.
This blueprint covers the lifecycle of user management: Provisioning, Auditingそして Deprovisioning.
Role-Based Access Control (RBAC)
Never share your master credentials. Instead, create individualized accounts with permissions tailored to each user's responsibilities. This ensures full audit trails and the ability to instantly revoke access when team members transition.
1. Accessing the Team Directory
The Team tab serves as the central command center for all user permissions.
Navigate
From your MultiLipi Dashboard sidebar, select チーム .
Audit View
You will see a unified table listing all active users, their assigned roles, access scope (specific domains), and current status (現役 vs. Pending Invite).
2. Provisioning Access (Inviting Members)
To onboard a new collaborator:
Initiate Invite
をクリックします Invite button in the top-right corner of the workspace.
Define Credentials
電子メール
Enter the corporate email address of the user.
Role Assignment
Select the appropriate privilege level (e.g., Administrator for full control, Contributor for translation editing only).
Project Scope (Optional)
Restrict the user to specific domains (e.g., Assign "Translator A" only to the German project).
Deploy Invitation
クリック Invite via Mail.
Security Note
The secure invitation link expires automatically in 30 days to prevent unauthorized access from stale links.
3. Managing Access Lifecycles
Governance is an ongoing process. You can modify or revoke permissions instantly as team structures change.
Modifying Roles (The "Edit" Function)
If a user needs elevated privileges or access to a new project:
Locate the user in the チーム table.
をクリックします Three Dots (⋮) icon in the Actions column.
選ぶ Edit.
Update their Role又は Project Assignment and click 変更を保存 . The new permissions apply immediately.
Revoking Access (Offboarding)
When a team member leaves or a contract ends, secure their account immediately:
Step 1
をクリックします Trash/Remove Icon in the Actions column.
Step 2
Confirm the removal.
影響
The user's session is terminated, and they lose access to the dashboard 瞬時に .
Summary: Collaboration Best Practices
| アクション | Best Practice |
|---|---|
| Role Assignment | コマンドの Principle of Least Privilege. Only grant Administrator access to trusted stakeholders. |
| Project Scoping | Isolate external agencies to specific projects to prevent them from viewing unrelated data. |
| Periodic Audits | Review the Team tab monthly to remove inactive users or pending invites. |
🔒 Security at Scale: By implementing granular RBAC, you ensure that your translation operations can scale globally without compromising data integrity or exposing sensitive project information to unauthorized team members.