The basic principle behind visibility and sharing
In struct-i-vio, people with very different tasks work together. That's why the platform follows a simple principle: what is relevant to your task is visible.
Authorizations arise from three levels that interact: the role in the company, the affiliation to specific projects and project-specific authorizations for sensitive or specialized tasks.
This makes it possible to accurately map who controls the company, who is responsible for an individual project and who works operationally on a project. This creates security, overview and practical collaboration.
Typical roles in the company
Public communication deliberately remains in understandable role models and not in technical stages.
| role | Typical access | Typical responsibility |
|---|---|---|
| administration | Company-wide setup, user management and central configuration | Prepare work areas, invite people and maintain structures |
| management | Overview of projects, evaluations and sensitive company areas | Control, decide and release |
| Project management or team management | Access to your own projects and project-related decisions | Coordinate teams, lead tasks and ensure progress |
| Project team | Access to your own projects and the relevant work areas | Collaborate, record, document and coordinate |
Additional rights within individual projects
Responsibility does not have to apply across the board to the entire company. struct-i-vio therefore supplements the role model with project assignments and project-specific authorizations.
Project management
The project management controls a specific project, organizes the team and can make project-related decisions directly.
Project permissions
Fine rights for times, expenses or other project-related processes are assigned directly in the project permissions.
Budget-related responsibility
For selected projects, budget-related rights can be added without opening up a general company-wide financial view.
Visibility follows responsibility
Not every person should see all projects or data. struct-i-vio is therefore oriented towards responsibility rather than an abundance of information.
Modules are activated accordingly
struct-i-vio does not show every menu item to every person. Which areas are visible depends on the company setup, activated modules and the respective role.
This means the interface remains clear and comprehensible. A project team needs different functions than management in everyday life, and that's exactly what the platform is designed for.
Clearly map several companies or companies
If a person works in several companies, companies or organizational areas, the rights may differ for each work area. Someone can take on management tasks in one organization and work exclusively on projects in another.
struct-i-vio shows this separation cleanly. When you change the work area, the view adapts to the respective context - an important advantage for corporate groups, holding structures or closely connected teams.
Additional rights around connected mailboxes
There are separate rights for the CRM email connection, which are deliberately assigned separately from general mailbox usage. This means that responsibility for company domains, access and separations remains clearly assigned. These rights are activated for each work area.
| Additional right | What it makes possible | Typical award |
|---|---|---|
| Manage company domain | Claim the company's email domains and verify them using a DNS entry - the basis for determining which mailboxes can be connected at all. | administration |
| Disconnect bound mailbox | Unlink a mailbox tied to the company domain from the CRM. Prevents bound mailboxes from being unauthorized. | Administration/Management |
| Manage mailbox access | Specify for each mailbox who can read, reply/send and manage access. Does not include automatic reading rights to the content. | Administration / mailbox manager |
Permissions in the Cold Leads module
The CRM module for cold leads distinguishes between six actions. All apply tenant-wide - no project reference. All six permissions are active, including bulk emailing.
| Authorization | What it makes possible | status |
|---|---|---|
| View cold leads | Call up list and detailed view, read conversation thread. | Active |
| Manage cold leads | Create, edit, archive cold leads; Request double opt-in. | Active |
| Delete cold leads | Permanently delete cold lead. Requires “understanding”. | Active |
| Raise to Warm Lead | Transfer cold leads from the outbound area into the sales pipeline. | Active |
| Send email | Send an individual email to a cold lead via the organization mailbox. | Active |
| Send mass email | Send a template email to several selected cold leads (with preview of skipped recipients and suppression/consent filter). Requires confirmed marketing consent per recipient. | Active |
What customers often want to know
Why don't I see a certain project?
Typically because you are not assigned to this project or your role there does not include a view of this area. This is part of the authorization concept and not an error.
Why can't I release times or expenses?
Approvals are consciously linked to responsibility. To do this, you need a suitable company role, project affiliation and the corresponding project-specific authorization.
Why don't I see budget information?
Areas close to budget are sensitive and are therefore only released for roles that they actually need for their task.
Can my role differ depending on the work area?
Yes. If you are active in several companies or societies, your responsibilities may vary depending on the context.
Why don't I see a specific email inbox?
Connected mailboxes have their own access control. You will only see a mailbox if you have been expressly granted reading permission - general mailbox permission alone is not enough. Contact the person responsible for mailbox access.
Why can't I send an email to a cold lead?
To do this, you need the “Send Email” permission in the Cold Leads module. In addition, an organizational mailbox must be connected for your tenant. If the contact has already clicked the unsubscribe link, the email address is blocked and can no longer be contacted.