# Database Restrictions and Adding New Dimensions

**URL:** <https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906>\
**Category:** Product Ideas\
**Created:** [February 13, 2019, 8:06pm UTC](https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906 "2019-02-13T20:06:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![aaron.roma](https://sea1.discourse-cdn.com/flex015/user_avatar/pug.phocassoftware.com/aaron.roma/32/285_2.png) [@aaron.roma](https://pug.phocassoftware.com/u/aaron.roma)\
**Post date:** [February 13, 2019, 8:06pm UTC](https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906/1 "2019-02-13T20:06:39Z")

</div>

There’s a big pain point I’ve ran into a number of times lately. It has to do with database restrictions and adding new fields in a database. Not sure if there’s an easier way to accomplish this or not.

We have a number of users with database restrictions in place. For instance, warehouse managers restricted to their warehouse, or territory managers restricted to their territory.

If we go in and change the design of a database - add a new dimension or measure for example, this new field is turned off by default for any user that already has a restriction in place. I then have to go to each user and edit their restrictions to turn on this new measure or dimension. This can become quite cumbersome.

Not sure of a solution, just wanted to point this out.

---

<div class="post-metadata">

**Author:** ![tim.janes](https://sea1.discourse-cdn.com/flex015/user_avatar/pug.phocassoftware.com/tim.janes/32/361_2.png) [@tim.janes](https://pug.phocassoftware.com/u/tim.janes)\
**Post date:** [February 18, 2019, 5:12pm UTC](https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906/2 "2019-02-18T17:12:12Z")

</div>

@aaron.roma Have you tried using Bulk Update under Admin-\>Users? Select multiple users, then go to “More” and “Bulk Update”. This makes it easy to change restrictions across multiple users at once. I came across this recently as we added new measures and properties, too.

![image](https://us1.discourse-cdn.com/flex015/uploads/phocassoftware/original/1X/ba6fb4891506ea7bfe045067e1f2ee638325d0a3.png)

---

<div class="post-metadata">

**Author:** ![aaron.roma](https://sea1.discourse-cdn.com/flex015/user_avatar/pug.phocassoftware.com/aaron.roma/32/285_2.png) [@aaron.roma](https://pug.phocassoftware.com/u/aaron.roma)\
**Post date:** [February 18, 2019, 7:41pm UTC](https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906/3 "2019-02-18T19:41:18Z")

</div>

I have tried it. The issue with that is that it blows away their existing restrictions. So while I can use the Bulk Update to add the new dimension to the users, they lose their restriction to their location/area/region, etc.

---

<div class="post-metadata">

**Author:** ![anon33838874](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@anon33838874](https://pug.phocassoftware.com/u/anon33838874)\
**Post date:** [March 21, 2019, 3:43am UTC](https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906/4 "2019-03-21T03:43:06Z")

</div>

Hi @aaron.roma. We currently have a couple of ideas to improve management of restrictions.

The first is to allow bulk adding of streams, measures, dimensions and properties to restrictions, similar to the bulk update approach.

The second is to allow administrators to specifically not restrict streams, measures, dimensions and properties so that any additions are always included.

Which do you think would best work for you?

---

<div class="post-metadata">

**Author:** ![aaron.roma](https://sea1.discourse-cdn.com/flex015/user_avatar/pug.phocassoftware.com/aaron.roma/32/285_2.png) [@aaron.roma](https://pug.phocassoftware.com/u/aaron.roma)\
**Post date:** [March 21, 2019, 1:01pm UTC](https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906/5 "2019-03-21T13:01:09Z")

</div>

In my specific case, the second option would work best. That’s only because I have not had many instances where I’ve needed to restrict a specific stream / measure / dimension from users.

Though I’d think the first option would offer more flexibility.

---

<div class="post-metadata">

**Author:** ![anon33838874](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@anon33838874](https://pug.phocassoftware.com/u/anon33838874)\
**Post date:** [March 21, 2019, 11:24pm UTC](https://pug.phocassoftware.com/t/database-restrictions-and-adding-new-dimensions/906/6 "2019-03-21T23:24:22Z")

</div>

Thanks for your response @aaron.roma. I’ll add some weight to the second option for you.