> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trubuild.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Settings and administration
> Manage organization details, branding, members and invitations, projects and packages, PTC style documents, technical round labels, and the activity log.
Click **Settings** in the sidebar to open the settings hub. This is where organization Owners and Admins run the workspace: organization details and branding, who has access, which projects and packages are active, the organization-wide defaults that shape evaluations, and the audit trail of changes.
Most controls here require the **Owner** or **Admin** organization role. Standard members work inside their assigned projects and packages instead. See [Roles and permissions](/get-started/roles-permissions) for the full access model.
The hub is organized into sections:
| Section | Use it to |
| -------------------------------- | ------------------------------------------------------------------------ |
| **General** and **Organization** | Set the organization name, logo, country, and currency |
| **Projects** | Edit, archive, and restore projects, and review project members |
| **Packages** | Edit, archive, and restore packages, grouped by project |
| **Members** | Invite people, change organization roles, and manage pending invitations |
| **Branding** | Upload your brand kit for a consistent workspace |
| **PTC style documents** | Upload organization-wide templates that shape drafted clarifications |
| **Technical round labels** | Standardize how technical evaluation rounds are named |
| **Activity** | Review the timestamped audit trail of administrative actions |
Each project and package also has its own settings, reached from the **Settings** button in the header of that project or package page. Use the settings hub for organization-wide administration and the per-project settings for day-to-day tender configuration such as documents and evaluation setup.
Two things you will not find in the hub: feature modules (Commercial Evaluation, Technical Evaluation, Tender Queries, Vendor Database, AI Chat) and sign-in policy (SSO, MFA, seat limits). Both are configured per organization by TruBuild, so raise changes with your TruBuild contact. See [Set up your account](/get-started/setup-account) for the module list.
## Organization details
Set the basics that flow into everything your team creates:
| Setting | What it controls |
| ------------------------- | ------------------------------------------------------------------------------- |
| **Organization Name** | The name shown across your workspace |
| **Organization Logo** | Your logo, with a live preview after upload |
| **Organization Country** | The default country offered when someone creates a new project |
| **Organization Currency** | The default currency offered when someone creates a new package in that country |
Click **Save** after changing a value. Getting country and currency right up front saves your team from correcting them package by package. Bid comparisons and BOQ totals are only meaningful when every submission in a package is held in one agreed currency, so set the default your commercial team actually tenders in.
## Projects
The **Projects** section lists every project with its country, member count, and status. For each project you can:
| Action | What it does |
| ----------------- | -------------------------------------------------------------- |
| **Edit settings** | Rename the project or change its country |
| **View members** | See and manage who has project-level access |
| **Archive** | Remove the project from active views without deleting anything |
Archived projects move to a separate **Archived Projects** list, where **Restore** brings one back. Archive closed-out tenders rather than leaving them in the active list: evaluators stay focused on live packages, and the full record (rounds, scores, clarifications, award rationale) remains available if a dispute or audit resurfaces the tender later.
## Packages
The **Packages** section groups packages under their parent project and shows each package's currency and technical/commercial weight balance. Per package you can **Edit** its details, **View members**, or **Archive** it. Archived packages sit in their own section with a **Restore** action.
The weight balance shown here is the split agreed at package creation between technical and commercial scoring, always totaling 100%. Check it matches your approved evaluation plan before any evaluation round starts, because it drives how combined scores are weighted. Changing weights mid-evaluation invites challenge from bidders and auditors.
## Members and invitations
The **Members** section shows current members, pending invitations, and lets you bring new people in.
Enter their email, pick an organization role (**Owner**, **Admin**, or **Member**), and click **Send Invite**. The invitation appears in the pending list until they accept.
The members table lists each person's email, name, and role. Change a role from the dropdown, or remove a member with the **X** button. Removing a member ends their access to the organization.
Pending invitations show the email, who invited them, and the role. **Resend** sends the invitation email again if it was missed or quarantined. **Cancel** withdraws the invite.
Give most evaluators the **Member** role and grant their working access at project or package level instead. Package-scoped roles keep commercial and technical evaluation strictly separated, which is the safest default for regulated or owner-led tenders. Organization roles do not grant tender access on their own; assign project or package roles after the invite is accepted.
Some organizations carry a member seat limit. If invitations stop going through because you have reached it, raise the limit with your TruBuild contact.
## Branding
The **Branding** section holds your brand kit:
* **Logo upload**: JPG or PNG, with a live preview of how it renders.
* **Color palette**: your brand colors.
Branding matters most when comparison outputs go in front of award committees, owner representatives, or external consultants. A consistent brand kit makes those outputs look like your documents, not generic tool output.
## PTC style documents
PTC style documents are organization-level templates and examples that shape how generated post-tender clarifications read. Upload past PTC schedules, clarification templates, or reviewer guidance once, and evaluation rounds across the organization draw on them so drafted clarifications match your team's language and format.
Pick the document type from the category dropdown so the file is filed correctly.
Drop the file in the upload zone. Standard document types are accepted (`.pdf`, `.docx`, `.doc`, `.txt`, and others).
These files guide the style and format of generated drafts. Keep the tender documents for a specific package in that package, not here.
Even one good example helps. A single well-written PTC schedule from a previous tender teaches the drafts your numbering style, your tone with bidders, and how you phrase scope-gap and exclusion queries.
## Technical round labels
Technical round labels standardize how technical evaluation rounds are named across the organization. For each label you set a round name and description, and you can **Add**, **Edit**, or **Delete** labels.
Use labels that mirror your evaluation plan, for example an initial scoring round followed by a post-clarification rescore. Consistent round names make it much easier for committees and auditors to follow how scores moved between rounds and why. See [Evaluation rounds](/platform/rounds) for how rounds work day to day.
## Activity log
The **Activity** section is the organization's audit trail. Each entry records the timestamp, the user, the action, and the entity affected, covering events such as members invited or removed and projects or packages created.
You can filter and search the log by action type, user, entity type, and date range. Reach for it when you need to reconstruct who changed what before an evaluation milestone, or to evidence access control during a probity or ISO audit.
## Related
Map enterprise users to organization, project, and package access.
Create the organization and invite your first team.
Plan governance and team design across a tender program.
See where round labels appear during evaluation.