Configuration of Cost Perimeters for a User

N.B. : The cost perimeters rely on the tag, cost partition and cost allocation unit concepts of Teevity. Read more about them here.

Read our introduction to the cost perimeter definition to have an overview of the feature including the company-wide configuration of cost perimeters.

In the Users management section of the Preferences section, in your users list, you can use the last icon (1) to open the cost perimeter configuration sidebar.

Static Cost Perimeter Definition

You will use the static perimeter when the user has access to a handful of cost allocation units and this list is rarely updated.

You just have to select the cost partition (1) and the cost allocation unit (2) you want to assign to the user and click on the "+" button (3).

The list of cost partition / cost allocation units assigned will be updated (4). When you have finished, click on the "Apply changes" button (5).

When applied, your changes are queued for processing. The user will shortly see his new perimeter in effect.

Dynamic Cost Perimeter Definition

You want to use the dynamic configuration when the user has access to an entire or partial subset of a cost partition and its cost allocation units are updated regularly. The definition is based on a list of tags and their values.

Imagine a Cost Partition "Environnement / Application / Component" where the Teevity tags are :

  • user:Environment
  • user:Application
  • user:Component

And the tag values are:

  • Development, Production
  • Project A, Project B
  • Frontend, Backend

Then the cost allocation units are:

  • Development / Project A / Frontend
  • Development / Project A / Backend
  • Production / Project A / Frontend
  • Production / Project A / Backend
  • Development / Project B / Frontend
  • Development / Project B / Backend
  • Production / Project B / Frontend
  • Production / Project B/ Backend

If you want to give access to a user for:

  • the Frontend component of the Project A and Project B for of the Production environnement and
  • the Backend component of the Project B in the Development environment

Which is the equivalent of a fixed cost perimeter, you will use this definition:

Interestingly, you can choose to give access to every component of the project A in the Development environment. If in the future a new component is added, the user will have automatically access to its costs:

But you can also use regular expressions to give access to a subset of cost allocation units of a cost partition. For example here we set the cost perimeter as all the components containing the word "frontend" in the project A for its production environment.

For more information about the syntax and how to test your regular expressions, please refer to the advanced filters of the dynamic cost explorer.

As in the fixed definition, you will need to click on the "Apply changes" button. Your modification is queued for processing, and the user will shortly see his new perimeter in effect.