What is it?
The Permissions at a submission level feature allows agencies to restrict user access to individual submissions in Indio based on Department and Profit Center data pulled directly from Epic. This enhancement builds on the existing integration with Epic’s organizational structure—previously limited to Region and Branch—by adding the remaining two permission levels used in Epic. With this feature enabled, agencies can control who sees or interacts with specific submissions, ensuring that access aligns with a user’s role, department, or business unit. This functionality is intended to mirror how Epic policies function, where access can be restricted using all four structure levels—Region, Branch, Department, and Profit Center—providing a familiar and consistent permissioning experience for enterprise users on the Indio side. This provides agencies on Indio with greater data security, supports regulatory compliance, and enables larger organizations to adopt Indio more broadly across complex office structures.
Why did we create this feature?
We created the Permissions at a submission level feature to address the needs of enterprise agencies that require more granular permissioning aligned with their existing Epic structures. Previously, Indio only supported Region and Branch-level access controls, which limited the ability to restrict user visibility within an account. However, This posed challenges for organizations that use all four Epic structure levels (Region, Branch, Department, and Profit Center) to manage policy access. Without similar controls in Indio, these agencies faced compliance concerns and were unable to adopt the platform broadly. By introducing Department and Profit Center-level access, we help organizations enforce stricter data security, meet internal privacy requirements, and confidently scale Indio across their offices.
Note: This feature is currently not enabled for all agencies. If you would like to test this feature for your agency please ensure that you have Applied Identity & Epic structures on Indio enabled. For more information please contact our support team.
---Before you begin---
Please ensure that you and you're agency/brokerage on Indio is utilizing Applied Identity to login to Indio. This is to ensure that your Indio account is linked with your Epic account in order to pull the Epic structures combination that are available to your user on Epic to Indio. Without this login connection you're user will be unable to access accounts or submissions that are restricted using Epic structures.
---Guide---
Creating A Submission With Structures
When the user is creating a new submission they will now see a section Assign Structure Access with 2 new available options:
Inherit Structure Combinations - This will use structure combinations that are available for the account the submission is being created on. This will typically be the default configuration selected. So if there are no structures on the account the account will not inherit any structures either.
Define Structure Combinations - This will allow the user to select structure combinations on the next step based on the account’s available structure combination to limit access to the submission being created.
Note:
In order for the "Assign Structure Access" to be visible the account must contain structures. Meaning that the client account needs to be either imported from Epic to Indio, via either the Epic Client Lookup Code or directly exported from Epic to Indio. Otherwise it will follow the normal Indio submission creation process.
If user selects Define Structure Combinations, they will be directed to the next step of setting the structures for the submission.
On this page, users must select options in a specific order to ensure that each choice reflects valid and available combinations. For example, once an agency is selected, only the branches associated with that agency will appear. The same logic applies to Departments and Profit Centers—each selection should be relevant based on the previous one.
Ex: If the agency “Simple Insurance Services”, has branches, “New York branch” and “Boston Branch” and agency “Tim’s Insurance Services”, contains branches “Chicago Branch” and “Austin Branch”. If the user selects the agency, “Simple insurance Services”, the available branch options should only be “New York Branch” and “Boston Branch”. The same concept applies for Department and Profit Center as well.
Once all the structures are selected in order, the user will have the option to delete the structures as well, but keep in mind that not deleting a structure in an inverse-orderly fashion will also delete the structure that comes after it, so that the user can select the proper combination.
Ex: If user deletes value on Branch field the Department and Profit Center values should clear out/be deleted as well, but not Agency.
Depending on whether the agency utilizes the feature: Integrations - Import Acord, there will be a next step of allowing the user to import policy data from Epic.
Editing Structures of a Submission
Once a submission has been created the user is able to edit the structures through the use of the actions menu. They will see the option to “Edit Structure Access”.
Clicking on “Edit Structure Access” will open a modal where the user will be able to either change the structure access from either Inherit or define structure combinations.
If the structures were previously defined, selecting inherit will delete the structures combination selected and use the structures available to the account.
Otherwise the user is able to delete and select new structure combinations if the structure access is set as “Define Structure Combinations”
Note:
If a user will limited structures access or no structures access is assigned to an account that contains structures, they will not be able to define structure access when creating or editing a submission. They can only create a submission by selecting the “Inherit Structure Combinations” option. This is because either that user lacks the structures associated with the account or doesn’t have any structures in the first place(no structures access user).
---FAQ---
What happens when a user without the correct permission tries to click into a submission from the activities tab?
The user will be redirected to an error page, informing them that they do not have the correct permissions to access that submission.
Furthermore, downloadable files from the activities section are now no longer links, instead they are bolded text. This is to ensure that users with the correct structures access are unable to download the file.
Will I be able to view documents or E-signatures from the document tab or E-signatures tab in an account if there is a document or E-signature in a submission with defined structures?
No, users will not be able to see documents or E-signatures that are part of a submission with defined structures, however they can see documents or signatures that aren’t part of a submission with defined structures in the tabs.
Will a user who does not have access to a submission with defined structures see that submission the submission Tab of Indio?
No, the submission tab on Indio will only show submissions that the user has access to.
How do I reflect updates from Epic to Indio for account structures?
When you update an account's structures on Epic, follow these steps to ensure the changes are reflected in Indio:
Navigate to the account in Indio for which the structures were updated.
If you are still on Epic, click the action menu button and select “Export to Indio.”
On the account details page in Indio, look for the option in the bottom left corner that says “Sync with Epic.” Click “Import from Epic.”
A drawer will open, displaying all the structures being pulled from Epic in the Account Information section.
Finally, select “Import from Epic” once more. Please note that this process may take a few seconds to complete.
Keep in mind that after updating structures in Epic, it may take a few minutes for the changes to sync properly into Indio.
How do I reflect updates from Epic to Indio for user structures?
If your user structures on Epic were updated while you were logged into Indio, please log out and then log back in to ensure the structures are accurately reflected.