Hierarchical Limit Policies
Innovative and Powerful

Flexible Limit Policies for Precision Access Control

Learn More

Why do we need Limit Policies?

Hierarchical Limit Policies are essential for setting and enforcing transaction restrictions based on quantifiable attributes at the individual or group level. They manage cumulative user, role, or group activities, such as training video watch time in an Electronic Learning Management system or the frequency of specific actions within a system.

Read More

These policies also support Approval Workflows by enabling conditional transaction commitment; where transactions exceeding predefined limits are temporarily recorded in the Authz1 system and fully committed upon approval.

Exploring Different Types of Limit Policies

Transactional Limit Type

Applies to any transaction performed by a user

Individual Limit Type

Applies to the sum of all transactions performed by a user over a configurable period of time

Aggregate Limit Type

Applies to the sum of all transactions performed by all the users belonging to a role or a group and, consequently, over a configurable period of time

A Closer look at Hierarchical Limit Policies

1

Individual and Aggregate Limit Policies can apply to a rolling time period, such as the last 30 days. They can also use a fixed period, like a calendar month.

2

Additionally, all limit policies can be permanent or temporary. Temporary ones include a start and end date.

3

All types of Limit Policies canoptionally be defined against a resource – such as a specific bank account

4

Limit Policies can apply at six levels Global, Enterprise-Defined Client Organization, Client-Defined Client Organization, Role, Group, User

Simple Use Cases

Explore key use cases demonstrating Authz1’s Hierarchical Limit Policies in action. While Authz1 handles complex scenarios, these examples illustrate its core functionalities.

First Use Cases

  • Limit AL1 applies to the set of all the users under the Client Company A hierarchy 
  • AL2 and AL3 limits apply to the set of User 5, Peter, User 6, User 7, Jane, User8, User 13, User 14  
  • AL4 and AL5 limits apply to the set of User 5, Peter, User 6
  • AL6 and AL7 limits apply to the set of User 7, Jane, User 8

Second Use Cases

  • Limit AL1 applies to the set of all the users under the Client Company A hierarchy 
  • Limit TL1 applies to all the individual users of User 1, User 2, User 3, User 4, User 9, User 10
  •  Limit IL1 applies to all the individual users of User 1, User 2, User 3, User 4
  • Limit AL8 applies to the set of User 1, User 2, User 3, John, and, similarly, User 4, User 9, User 10, User 11, User 12, Jane
  • Limit IL2 applies to all the individual users of User 9, User 10, User 11, User 12, Jane
  • Limit AL9 applies to the set of User 9, User 10, User 11, and, additionally, User 12, Jane
  • Limit AL10 applies to the set of User 3, John, User 4
  • TL2 and IL3 limits apply to John
  • Limit TL3 applies to all the individual users of User 11, User 12, Jane
  •  Limit TL4 applies to Peter

Third Use Cases

  • All the Limit Policies from Example 1 and Example 2 apply 
  • Jane’s transactions count against AL1, AL2, AL3, AL6, AL7 and AL8 limits
Scroll to Top