Permission reference

Permissions, levels and scopes

A permission answers the question "can this person open this part of BuildColab, and may they only look or also change things?". Each permission has two levels:

Permissions exist at two scopes, using the same list of permissions:

• Company level is the member's role, set on the Roles screen. It applies across the whole company: company pages such as Nomenclatures, Partners, Requests, Report Register and Admin, and what the server lets the person save anywhere in the company.
• Project level is the member's access in one project, set in that project's Project team → Access level (Достъпност). It decides which project sidebar entries, screens and buttons the person sees in that project. Each project can be different.

Above both sits the company's plan. A permission the plan does not include does not work for anyone, whatever the role or project access says. A member without an active licence on a paid plan falls back to the Free plan's set. See Subscription, plans and billing.

How company role and project access work together

These rules decide what a member can actually do inside a project:

1. Project access is copied from the role when the member is added to the project. At that moment BuildColab copies each permission and level of the member's role into their access for that project.
2. The copy is not re-synced later. If you later change the role's permissions, or give the member a different role, their access in projects they already belong to stays as it was. Projects they join afterwards get a copy of the new role.
3. The person who creates a project gets every permission at Edit in that project, regardless of their role.
4. Project access can be changed per member and per project in Project team → Access level, without touching the role or other projects. The company owner's project access cannot be edited; the owner always has full access, and a member who becomes owner by transfer gets Edit on all company projects.
5. In practice you need the permission at both levels, and the lower level wins. The project access decides what you see in the project; the company role decides what the server accepts when you save. If your project access says Edit but your role says View, you see the edit buttons but saving is refused with an access error. If your role says Edit but your project access says No access, the entry is locked in that project.
6. Company-only permissions (Members, Received bid requests, Partners, BORO Skills (author)) act only through the role. The project access panel may list them, but setting them there changes nothing.

1. The panel title Access level and the member's read-only name, e-mail and Role.
2. The Features column lists each permission.
3. The Access column shows Edit, View or No access for this project. For any member other than the company owner, an Edit button in the panel header switches the panel to edit mode.

How to change a member's access in one project

1. Open the project and click Project team (Проектен екип) in the project sidebar.
2. Click the member. The Access level (Достъпност) panel opens.
3. Click Edit (Редактирай). Each row turns into a switch with None (Няма), View (Преглед) and Edit (Редакция).
4. Set the levels you need and click Done (Готово) to save. At least one permission must stay above None ("Give access to at least one feature.").

Changing project access needs the Projects (Проекти) permission at Edit, both in your role and in your access for that project. More about the project team is in Project team and access.

How missing access shows in the app

The Request access (Поискай достъп) button on these pages is marked "Coming soon" and does nothing yet; contact your administrator directly.

Default roles at a glance

E = Edit, V = View, — = not included. "Free plan" shows whether the permission works on the Free plan. Each company has its own copy of these roles, so check your actual roles on the Roles screen.

1. The selected role in the role list.
2. Features and access lists only the permissions the role has, each with an Edit or View pill.

Every permission in detail

Each entry below names the permission exactly as in the role editor, in English and Bulgarian.

Members (Членове)

Editing the company profile and transferring ownership are reserved for the company owner, whatever the role says. See Members, invitations and licences.

Outgoing bid requests (Изходящи запитвания)

See Creating and sending an offer request.

Received bid requests (Получени запитвания)

See Incoming offer requests (subcontractor side).

Offers (Оферти)

See Working in the BoQ editor.

Nomenclature (Номенклатура)

See Company library (nomenclatures).

Resource analysis (Ресурсен анализ)

See Resource analysis.

File manager (Файлов мениджър)

See Folders, uploading and navigation.

Projects (Проекти)

See Project list and creating a project.

Partners (Партньори)

See Partners.

Execution (Изпълнение)

See Contracts: signing, details and history.

Contract changes (Промени по договор)

See Change orders and extensions.

Budget preparation (Изготвяне на бюджет)

See Investment budget.

Reports (Отчети) — payment applications

See How a payment application works.

Financial dashboard (Финансово табло)

See Financial dashboard: committed, certified, margin.

Schedule (График)

See Schedule.

Contracting schedule (График на договаряне)

See Contracting schedule and packages.

BORO Skills (author) (BORO умения (автор))

See Skills.

Features without a permission

Some parts of BuildColab are not controlled by any permission in the role:

• Work tasks (Работни задачи): access follows each board's sharing; there is no plan lock.
• Meetings (Срещи): project meetings are open to the project team; company meetings to the company's members. There is no plan lock either; the menu entries are missing only where the module is not switched on in your environment.
• Admin → Organization and Subscription: open to every member (individual cards and actions have their own rules).
• BORO chat and the calendar: open to every member. BORO can only do what your own permissions allow; credits are shared by the company.

Editing the company profile and transferring ownership are reserved for the company owner and cannot be given to a role.

Common questions

Related

• Roles
• Project team and access
• Members, invitations and licences
• Subscription, plans and billing