At its core, Inkit provides a Software as a Service product that lets you generate PDFs and other paperless file formats from HTML. However, the product extends far beyond PDF generation. Inkit Render is of great interest to those who seek compliance and security-focused solutions.
For instance, Inkit has an elaborate security & management layer that provides an array of features. Examples are user permissions, admin controls, audit logs, document expiration, the ability to create HTML templates in which you can inject data, and more.
Zoomed out, the Inkit product comprises two primary components: the web application and the Render API.
The web application is accessible through a web browser and lets users manage API keys, set user roles and permissions, restrict data access, onboard their team, and view their rendered PDFs, and so on.
Through the API, systems can integrate Inkit's DocGen platform into their data-to-document pipeline. Thus, granting them the ability to create PDFs at scale securely.
A powerful feature of Inkit’s management & security layer is that organizations can set up their internal systems with varying permissions and authorization. The result is integrated systems that only behave within their permitted boundaries.
Furthermore, the management & security layer is extensively customizable. Meaning, you can set up the Inkit environment to fit your organization’s specific needs.
The following overview gives a brief insight into Inkit Render’s core features. If you wish to read more about Inkit Render, refer to the Inkit Render page or the documentation
Inkit Render lets organizations create PDFs at scale without having to set up costly, maintenance-heavy infrastructure. With the appropriate permissions, users or API keys can perform several PDF generation operations.
- Creating PDFs
- Retrieving PDFs
- Updating PDFs
- Deleting PDFs
If you would like to generate your first PDF with Inkit Render, please read the following topic:
Document expiration is the method through which users can specify when a document must be hard-deleted.
There are two ways you can set up a document for expiration.
- Expiration after a specified number of views
For example, you could use expiration after n number of views to create one-off documents.
- Expiration on a specified date
Particularly useful for compliance with data law. Many organizations are mandated to delete data after a legally defined time period. You could make confidential documents, like patient data, auto-expire at a specified date with this feature.
Alerts, commonly referred to as webhooks in the Inkit environment, tell your systems that an event has occurred. There are many events to which your systems can subscribe.
For example, when setting up your integration with Inkit Render, you may wish to get notified about PDF render completion. Doing so would let you retrieve the created render exactly when it is complete. Additionally, you may want to be notified when a user attempts (and fails) to access confidential data.
Each user or API key has its permissions through the roles they have been assigned.
User & API key roles can be created and modified by users with the appropriate permissions. By default, only Admins can create new user roles and select the appropriate permissions.
Roles & permissions are part of the management & security layer and give your organization the option to determine authorization at different levels.
Folders are always private. Users can create ‘shares’ to give access to specific folders to other users. Only users with the appropriate permissions can share folders.
Templates are pre-defined HTML files that you can create and with which you can dynamically inject data. This feature is of great value to organizations with standard document templates with specific data injection needs — for example, bank statements, patient prescriptions, or even automatic reports.
Get the data you need, populate your template, and streamline your document generation process at scale.
Updated 5 months ago