Vendors
In the Vendors section, you manage providers, organizations, or developers from whom applications or operating systems originate.
This information serves categorization, traceability, and filtering within the OpenVLE infrastructure.
Where can I find this section?
Via main menu: Infrastructure → Vendors
Alternatively accessible via: Linked from Applications or Operating systems
Features at a glance
- View, create, edit, and delete vendor entries
- Assign vendors to applications or operating systems
- Filter content by vendor
- Centrally maintain consistent naming across the entire system
Important fields at a glance
| Field name | Description |
|---|---|
Description | Optional brief description of the vendor, e.g. location, product lines, or supported platforms. |
Name | Name of the vendor or organization, e.g. "inett GmbH", "Proxmox Server Solutions GmbH", or "Decisio". |
Creating a vendor
- Open the Infrastructure → Vendors section from the main menu.
- Click Add to create a new vendor.
- Enter a name and a description for the vendor.
- Save the vendor.
- Then switch to the Applications or Operating systems tab to add the desired objects.
Editing a vendor
- Open the Infrastructure → Vendors section from the main menu.
- Find the desired vendor in the list.
- Click Edit, or open the context menu of the vendor and select Edit.
- The form displays all current data of the vendor.
- Adjust the desired fields -- for example Name or Description.
- Save the changes.
Deleting a vendor
- Open the Infrastructure → Vendors section from the main menu.
- Find the desired vendor in the list.
- Click Delete, or open the context menu of the vendor and select Delete.
- Confirm the deletion in the displayed dialog.
- The vendor is then permanently removed.
Only vendors that are no longer assigned to any application or operating system can be deleted.
Example or use case
An administrator wants to create a new application from a vendor that has not yet been recorded.
She opens the Infrastructure → Vendors section, clicks Add, and enters:
- Name: The Document Foundation
- Description: Non-profit organization behind LibreOffice
After that, this vendor can be directly selected when creating the application "LibreOffice".
Notes / special considerations
- Vendors are linked to applications and operating systems.
- Consistent maintenance of vendors facilitates later filtering and reporting.
- It is recommended to keep vendor names unambiguous (e.g. "Microsoft Corporation" rather than just "Microsoft").
Relationships to other objects
Many objects in OpenVLE are related to other elements within the system. The following overview shows which relationships exist and whether they trigger certain automations.
| Object | Description | Automatic behavior |
|---|---|---|
| Applications | Any number of applications can be assigned to a vendor. | No automations. |
| Changelogs | All changes to the object are automatically logged. | Automatic removal when the object is deleted. |
| Operating systems | Any number of operating systems can be assigned to a vendor. | No automations. |
| Permissions | Object-specific permissions can be assigned directly to the object. | Automatic removal when the object is deleted. |
| Tags | Objects can be tagged with any number of tags to categorize or filter them. | Automatic removal when the object is deleted. |
Required permissions
The permissions required for actions can be assigned via roles or individually. If you lack certain rights, the corresponding functions in the user interface are hidden or disabled.
| Action | Required permission | Path | Additional information |
|---|---|---|---|
| View vendors | vendors_read | / or /<objectID> | |
| Create vendors | vendors_create | / | |
| Edit vendors | vendors_update | / or /<objectID> | |
| Delete vendors | vendors_delete | / or /<objectID> |
Example:
/4a3bc312-d1af-4b3f-b222-f5e9cecbf007 – This gives the user access to this single object only.If the path / is used, the permission applies globally to all objects of this type.
For *_create permissions, only the global path / is allowed.