Reports and alerts
Tagaris answers the questions an asset register exists for: what do we have, where is it, what is it worth, and what needs attention soon.
Built-in reports
The Reports page has fifteen ready-made reports: assets by status, category, location, person and manufacturer, warranties and licences due, value with depreciation, disposals over the last twelve months, value by location, contracts due, a vendor summary of spend and live contracts, spend by vendor and by category for a period you choose, and open purchase orders. Every report exports to CSV and prints cleanly. The two by-location reports roll up the location tree, so a site's row includes its rooms and racks alongside its own figures.
Running a report or exporting is a permission of its own, "Run reports and export data". Editors and administrators have it; view-only people do not, unless an access group gives it to them. The same permission covers CSV and JSON exports of the register, contracts and orders. A person limited to particular sites sees only those sites' assets in every report.
Custom report builder
The report builder filters the register on your own terms and picks exactly the columns you want, with its own CSV export.
Scheduled reports
Tagaris can email a summary of changes and upcoming renewals weekly or monthly. Choose the frequency in Settings, or send one immediately to check the format. Scheduled reports are free on every plan.
The daily digest
Every install, free or paid, can send a daily digest listing what needs attention: warranties expiring, software licences and domains due for renewal, contracts nearing the last day to give notice, assets past their replacement age, stock below its minimum quantity, API keys approaching their expiry date, and issues raised since the last digest (each is mentioned once, high priority first). It also warns before credentials lapse: your Tagaris licence, the single sign-on client secret, and any expiry date you record on an integration credential (the Jira API token, or the Intune and Jamf client secrets, each connector card has an optional expiry field). It sends through whichever email transport you have configured.
Webhooks, tickets and calendar
The Alerts tab in Settings can also post the digest's findings to a Slack or Microsoft Teams webhook, and publishes a calendar feed of upcoming renewal dates, contract act-by and end dates included, that Outlook or Google Calendar can subscribe to.
With the Jira integration connected, the Alerts tab offers "also raise a Jira ticket": each digest that fires creates one issue in your configured project carrying the same items, so renewals land in the service desk queue as well as inboxes. One ticket per digest, never one per item.