Understanding Project Management in Fubwer

Within Fubwer, a "Project" is a dedicated workspace under your organization's Contract. It's designed to manage a specific set of translation tasks, typically centered around a particular document, product, campaign, or regulatory filing.

Each project serves as a crucial container for:

• Translation Keys: The individual segments of text (source text and their corresponding translations) that make up your content.
• Project Members: The team of users (Admins, Editors, Viewers) assigned to work on or review the translations within that specific project.
• Project Settings: Configurations like source language, target languages, and specific metadata relevant to the project's content.

This structure allows for focused collaboration, precise tracking, and granular control over your translation assets.

When you navigate to your organization's Contract details page (e.g., from the main dashboard), you'll find a central hub listing all projects associated with that contract. This page is key for oversight and initiating project-level actions.

What Users Can Expect:

• Visibility: Users will see a list of projects they have access to, based on their roles (Contract Admin, Project Admin, Editor, or Viewer).
• Project Cards/List: Each project is typically displayed with summary information (name, status, languages) and provides entry points to view detailed project information or manage members.

Creating New Projects:

Users with appropriate permissions, specifically Contract Administrators and project-level Admins (who are often designated by Contract Admins), can initiate the creation of new projects directly from this contract hub.

When a new project is created, it inherits the security and organizational context of the parent contract. The creator is typically assigned as an initial Project Admin, empowering them to further configure the project, manage its content (translation keys), and assign other users (Editors, Viewers) to collaborate on the translations.

Fubwer employs a robust role-based access control (RBAC) system to ensure that only authorized individuals can access and modify project data. This is paramount, especially for financial institutions handling sensitive information.

• Granular Access: Permissions are defined at the project level. A user might be an Editor in one project and a Viewer in another, or have no access to other projects within the same contract.
• Role Hierarchy: Higher-level roles (like Contract Admin) often inherit the capabilities of project-level administrative roles for projects under their contract.
• Auditability: Actions within projects, such as key creation or translation updates, are typically associated with the user who performed them, aiding in traceability.

Managing Project Members & Its Importance:

Project Admins (and Contract Admins overseeing the project) are responsible for adding and managing users within their specific projects. This involves assigning appropriate roles (Admin, Editor, Viewer) to team members.

Why this is critical for financial institutions:

• Principle of Least Privilege: Users are granted only the access necessary to perform their duties, minimizing the risk of accidental data modification or unauthorized access to sensitive translation content.
• Confidentiality: Ensures that specific translation projects, which might pertain to confidential financial reports or strategies, are only accessible to the designated team.
• Compliance: Helps in adhering to internal governance and external regulatory requirements regarding data access and segregation of duties.