Getting Started
The Blueprint application is designed to be user-friendly and fully configurable. This means that following deployment the system can be tailored to your needs by utilising the features within the application.
We will work with you to configure the base application as part of your data migration so a lot of this will be covered within the project plan and handled by Tiger Eye. For customers who wish to carry out this work themselves these are the key steps to getting a working application.
Licencing
First step will be to upload a valid licence to enable the application to run. Further information can be found within About.
Application Roles
The system will be pre-configured to integrate with your Azure Entra ID which enables user single sign-on. Following this you will need to create Application Roles and assign individual Users and/or Groups for the Application.
There are no restrictions on the number of Roles however, we normally recommend at least the following:
Administration - configure a role for the users managing the Blueprint application which will likely need to include permissions for all of the configuration settings and the Document/Bundles updates
Users - this role will cover the majority of users within the firm and will allow them to nominate, search and retrieve knowledge but not normally the ability to manage the configuration or edit/delete Documents and Knowledge Bundles
Further details on how to create these roles can be found within Application Roles.
*As part of deployment we will configure a maximum of 3 ‘Power Users’ who are granted every permission within the application and can access all features before Application Roles are created.
Fields and Contexts
You will need to create metadata Fields that will appear in several areas of the application via the Context settings. These will enable users to add/edit metadata that is attributed to Documents and Knowledge Bundles.
There is no restriction on the number of Fields you create and there are multiple Field types and data restrictions that can be applied.
Further details on how to create and administer these can be found within Fields andContexts.
Document Stores
The system is designed to allow users to nominate Knowledge from either their local file storage or iManage libraries. You will need to configure the following:
A Source Document Store - This will be the iManage library(ies) where users can nominate documents from
A Knowledge Document Store - This will be the iManage library where Blueprint will save copies of the original Documents and Blueprint will access these copies
Further details on how to configure these can be found within Document Stores.
Practice Groups
Each Document nominated to Blueprint will be assigned to a Practice Group, this is a group of people who own, review and maintain the Documents assigned to the group.
There is no restriction on the maximum number of groups you create. However, there does need to be at least one configured.
Further details on how to configure these can be found within Practice Groups.
Optional Configuration
There is additional configuration available which is implemented out of the box but you may wish to review and amend:
Appearance - Adjust the colour scheme and logo. More information can be found within Appearance.
Feature Enablement - Disable or enable certain features within the application. More information can be found within Feature Enablement.
Notification - Email notifications are configured for set events. More information can be found within Notifications.
Create Knowledge
As part of Deployment and Migration all of your existing Knowledge can be imported into the Blueprint application. If you are just starting out with storing Knowledge and haven’t asked us to import data then you will need to start creating Documents within Blueprint.
In order to add Documents to Blueprint you will need to use the application and further information can be found within Nomination.
You can also create groups of Documents via Knowledge Bundles in order to group and organise collections of related Knowledge. Further information can be found within Create Knowledge Bundle.
Summary
Once the above steps are completed you will have an active application with Knowledge stored within and organised. This information will be searchable and enable important information to be shared across the firm.