Licence Tab
Would be great to have a Licence tab for each client where you can enter all licences the client has including licence keys, expiry dates, usernames, passwords and which end user is using a particular licence.
You are then notified when a licence is expiring so can action the renewal.
Log in to comment and vote
Comments4
huzaif
We have a feature called “structured docs” in the product which should address this need.
In Settings → Documents, you can setup a new Structured Document template. There you can define all the fields you wish to catalog for that template. You can create one for each concern, like license, printers, credentials and more.
Back to the documents section, when you open documents for your customers (using client focus), you will see these structured docs. You can then manage the information in the format you defined.
Sapphire Horizon
Thanks Huzaif. Will look in to it. Do structured documents notify you when a licence is expiring or due for renewal?
Mikel from Gorelo
Not at this stage but we will be releasing an ‘Expirations’ feature in the future that will tie back to anything with an expiration E.g warranty, contracts, domains, structured docs etc. :)
Ivory Gust
Hi Mikel,
Expirations has been released but currently only supports asset warranties, contracts, and domains. It would be great if Structured Documents were also supported, or alternatively a dedicated Licenses item at the Client level as per the original request.
Real-world example: some clients have certificates/licenses requiring manual annual or bi-annual renewal — e.g. the Intune Apple MDM Push Certificate (annual) and Samsung Knox Platform for Enterprise license (bi-annual). These need expiry tracking with automated alerts/tickets at the Client level.
The only current workaround I can see is creating a custom Hardware Asset Type and using the Warranty Expiry field, but this hits another limitation: Expirations only supports filtering by asset type with no exclude option. So instead of 2-3 rules using exclusions to cover all asset types, I'd need a separate rule for every single type — which doesn't scale.