Administration¶
Installation¶
- Open Administration > Extensions.
- Upload the Ebla Assets Management package.
- Complete installation and allow EspoCRM to rebuild.
- Confirm that the Asset MS navbar groups, Roles, Dashboard Template, label template, scheduled job, and business scopes are available.
- Assign a Role and deploy the dashboard before testing as a non-admin user.
The package requires EspoCRM 10.0 or newer and PHP 8.1 or newer.
Installed Roles¶
Ebla Assets Management seeds three access profiles.
| Role | Type | Intended use |
|---|---|---|
| EblaAssetMS Administrator | Role | Full Ebla Assets Management configuration and operations; it does not make a user an EspoCRM system administrator |
| EblaAssetMS Manager | Role | Daily inventory, custody, reporting, calendar, and reference-data work |
| EblaAssetMS Self-Service | Portal Role | Restricted access for a Portal User linked to a Contact |
Treat these as starting points. Review scope access, record access, field ACL, Teams, and Portal restrictions for your organization before production use.
Recommended setup order¶
- Create Asset Statuses and set their meta status.
- Create hierarchical Asset Categories for each inventory type.
- Create Asset Locations and Departments.
- Create Accounts for manufacturers, suppliers, and Companies.
- Create Contacts for people who can receive or request inventory.
- Create depreciation schedules and Maintenance Types if needed.
- Create model-specific Asset Field Sets.
- Create Asset Models and attach the correct Field Set.
- Create or import Assets and quantity-based inventory.
- Create Licenses and their License Seats.
This order reduces incomplete links and prevents Asset records from being created before their operational rules are ready.
Statuses and categories¶
An Asset Status includes a meta status used by the operational presets and checkout rules. Typical meta statuses are Deployable, Pending, Undeployable, and Archived.
Categories are hierarchical and identify the inventory type. Category settings can also control requestability and whether Contact checkout requires acceptance.
Asset Field Sets¶
An Asset Field Set defines specifications that apply only to selected Asset Models. A laptop can require Processor and Memory fields while a monitor uses Panel Size and Resolution.
A Field Set can contain:
- Field key and user-facing label.
- Field type and options.
- Required and read-only rules.
- Layout order.
- Role audiences.
- An active flag and schema version.
Assign the Field Set to one or more Asset Models. When a user creates or edits an Asset, Ebla Assets Management resolves the Model's definition, validates the values, and makes the typed values available to filtering and reports.
Grant Field Set create or edit access only to trusted configurators. They do not need EspoCRM system-administrator access to use the bounded Ebla Assets Management builder.
Deploy the dashboard¶
Installation creates the Ebla Asset MS Dashboard template and adds the Asset MS tab to the default dashboard definition.
For an existing user:
- Open Administration > Dashboard Templates.
- Open Ebla Asset MS Dashboard.
- Use Deploy for Users or Deploy for Team.
- Select the intended users or Team and confirm deployment.
- Sign in as a target user and verify the Asset MS tab, widget values, and clickable filters.
Assigning a Dashboard Template and deploying it are different operations. Deployment copies both the layout and dashlet options to user preferences.
Layouts and fields¶
Use EspoCRM Layout Manager to adjust list, detail, edit, and Mass Update layouts.
- Assigned User and Teams already belong to the side panel. Do not duplicate them in the main detail layout.
- Add ordinary editable fields to Mass Update when users need them.
- Do not expose custody state, assigned parent, availability counters, immutable history, or computed fields for direct mass editing.
- Keep action columns such as Checkin/Checkout on the intended list only.
Ebla Assets Management fields include tooltips in English and Arabic. A user can select the preferred language from EspoCRM Preferences when that language is enabled.
Global search¶
The installer preserves the existing globalSearchEntityList and adds the
main searchable Ebla Assets Management business scopes. Reference-only, immutable, and
internal helper records are intentionally omitted.
After changing global search configuration, test with a non-admin Role to confirm that results remain relevant and ACL-restricted.
Deleted Assets¶
The administrator-only Deleted Assets page lists soft-deleted Asset records that remain recoverable. An EspoCRM administrator can restore one record or a selected group.
Restoration uses EspoCRM's record restoration behavior. Records can no longer be restored after the system cleanup permanently removes them.
Optional Ebla extensions¶
| Extension | Ebla Assets Management enhancement |
|---|---|
| Ebla Dash Pro | Colored numeric KPI dashboard widgets; Ebla Assets Management keeps its own chart, summary tables, and core fallback |
| Ebla Link Pro | Richer linked-record presentation and inline child-record management where configured |
| Ebla Progress Bar | Visual Remaining and % Remaining fields on Licenses |
These extensions remain separate. Missing an optional extension must not prevent core Ebla Assets Management records and operations from working.
Troubleshooting¶
The Asset MS dashboard tab is missing¶
Deploy the Ebla Asset MS Dashboard template to the affected user or Team. Then refresh the browser and confirm that the Role can read the dashboard scopes.
A custody button or mass action is missing¶
Check all of the following:
- The user has edit access to the scope and record.
- The record state allows the operation.
- Specific rows are selected for a mass custody action.
- The action is included by the installed Ebla Assets Management client metadata.
Custody actions intentionally do not run against an unlimited “all filtered results” selection.
A field is not available in Mass Update¶
Add ordinary editable fields through Administration > Layout Manager > [Scope] > Mass Update. Custody-controlled and computed fields should remain unavailable.
Dashboard KPIs look different¶
Colored numeric KPIs require Ebla Dash Pro. Without it, Ebla Assets Management uses the available core and extension-owned dashboard fallbacks.
License remaining values are plain numbers¶
Install and enable Ebla Progress Bar for the visual display. The stored Remaining and % Remaining values still work without it.
Model-specific fields do not appear¶
Confirm that the Asset Model has an active Field Set, the current Role can read the definitions, and the user has field access. Rebuild EspoCRM after module metadata changes.