Hi Community ,

I have had an observation on my org - whenever any new Integration is activated (e.g. app foundry or copilot ) , the asssociated permissions are directly getting  attached to Admin and Master Admin roles . How can I stop this from happening?

SInce Admin roles are assigned to some developers in my org, all such people are getting these new integration permissions as well, hence billing increases towards consupmtion of these integrations .

For now , i have done two things : 1) defaulted back the Admin and Master Admin role to original , and 2) created separate roles for new Integrations and giving them to people on a need basis only . However, I am not sure whether this will prevent any future integrations to be associated to these roles !

Anybody else faced the same issue , if yes please guide .

Regards

Garima.

Hi Community ,

I have had an observation on my org - whenever any new Integration is activated (e.g. app foundry or copilot ) , the asssociated permissions are directly getting  attached to Admin and Master Admin roles . How can I stop this from happening?

SInce Admin roles are assigned to some developers in my org, all such people are getting these new integration permissions as well, hence billing increases towards consupmtion of these integrations .

For now , i have done two things : 1) defaulted back the Admin and Master Admin role to original , and 2) created separate roles for new Integrations and giving them to people on a need basis only . However, I am not sure whether this will prevent any future integrations to be associated to these roles !

Anybody else faced the same issue , if yes please guide .

Regards

Garima.

Hi Garima,

Can you check if you have Automatically backfill roles with new permissions enabled in your org? Disabling this should stop it form backfilling the permissions and allow you to Manually assign the permissions to the roles required.

Hi Community ,

I have had an observation on my org - whenever any new Integration is activated (e.g. app foundry or copilot ) , the asssociated permissions are directly getting  attached to Admin and Master Admin roles . How can I stop this from happening?

SInce Admin roles are assigned to some developers in my org, all such people are getting these new integration permissions as well, hence billing increases towards consupmtion of these integrations .

For now , i have done two things : 1) defaulted back the Admin and Master Admin role to original , and 2) created separate roles for new Integrations and giving them to people on a need basis only . However, I am not sure whether this will prevent any future integrations to be associated to these roles !

Anybody else faced the same issue , if yes please guide .

Regards

Garima.

Hello Samuel,

thank you for this tip. The permission is off in our org.  Does this also prevents, that the new roles and permissions get assigned to Admin and Master Admin roles only despite this option?  Can you clarify it? 

Thx in advance. 

Petr 

Hi Garima,

Can you check if you have Automatically backfill roles with new permissions enabled in your org? Disabling this should stop it form backfilling the permissions and allow you to Manually assign the permissions to the roles required.

Hi Community ,

I have had an observation on my org - whenever any new Integration is activated (e.g. app foundry or copilot ) , the asssociated permissions are directly getting  attached to Admin and Master Admin roles . How can I stop this from happening?

SInce Admin roles are assigned to some developers in my org, all such people are getting these new integration permissions as well, hence billing increases towards consupmtion of these integrations .

For now , i have done two things : 1) defaulted back the Admin and Master Admin role to original , and 2) created separate roles for new Integrations and giving them to people on a need basis only . However, I am not sure whether this will prevent any future integrations to be associated to these roles !

Anybody else faced the same issue , if yes please guide .

Regards

Garima.

Another area to be watchful of is where a permission is for a range of features.

For example if you have users with Assistants> All Permissions, when Copilot was released every user with that permission would automatically get Copilot permissions and therefore count at the higher token rate. Therefore it is always worth considering whether users should have the "All" permissions. Due to older permissions not having the granularity of new ones sometimes the only option is the "All" permission.

Hello Samuel,

thank you for this tip. The permission is off in our org.  Does this also prevents, that the new roles and permissions get assigned to Admin and Master Admin roles only despite this option?  Can you clarify it? 

Thx in advance. 

Petr 

Hi Garima,

Can you check if you have Automatically backfill roles with new permissions enabled in your org? Disabling this should stop it form backfilling the permissions and allow you to Manually assign the permissions to the roles required.

Hi Community ,

I have had an observation on my org - whenever any new Integration is activated (e.g. app foundry or copilot ) , the asssociated permissions are directly getting  attached to Admin and Master Admin roles . How can I stop this from happening?

SInce Admin roles are assigned to some developers in my org, all such people are getting these new integration permissions as well, hence billing increases towards consupmtion of these integrations .

For now , i have done two things : 1) defaulted back the Admin and Master Admin role to original , and 2) created separate roles for new Integrations and giving them to people on a need basis only . However, I am not sure whether this will prevent any future integrations to be associated to these roles !

Anybody else faced the same issue , if yes please guide .

Regards

Garima.

Hi Garima,

Can you check if you have Automatically backfill roles with new permissions enabled in your org? Disabling this should stop it form backfilling the permissions and allow you to Manually assign the permissions to the roles required.

Hi Community ,

I have had an observation on my org - whenever any new Integration is activated (e.g. app foundry or copilot ) , the asssociated permissions are directly getting  attached to Admin and Master Admin roles . How can I stop this from happening?

SInce Admin roles are assigned to some developers in my org, all such people are getting these new integration permissions as well, hence billing increases towards consupmtion of these integrations .

For now , i have done two things : 1) defaulted back the Admin and Master Admin role to original , and 2) created separate roles for new Integrations and giving them to people on a need basis only . However, I am not sure whether this will prevent any future integrations to be associated to these roles !

Anybody else faced the same issue , if yes please guide .

Regards

Garima.

Hi Community ,

I have had an observation on my org - whenever any new Integration is activated (e.g. app foundry or copilot ) , the asssociated permissions are directly getting  attached to Admin and Master Admin roles . How can I stop this from happening?

SInce Admin roles are assigned to some developers in my org, all such people are getting these new integration permissions as well, hence billing increases towards consupmtion of these integrations .

For now , i have done two things : 1) defaulted back the Admin and Master Admin role to original , and 2) created separate roles for new Integrations and giving them to people on a need basis only . However, I am not sure whether this will prevent any future integrations to be associated to these roles !

Anybody else faced the same issue , if yes please guide .

Regards

Garima.