Method Community

So far I've only been able to figure out how to set permissions at the app level...

I think I follow screen permissions, although it appears as if that feature is notavailable yet. Chapter 2B in 101 customization did not elaborate on this.

Are there or will there ever be permissions at the section and object level?

Hello Mahlon,

Here's my answer. In order to set the permissions at the app level, please follow the steps mentioned below:

- Click on the Manage Apps option on the Left hand side Method menu.

- Choose the App you want to set the permissions and Click Edit App.

- Click on the Permissions on the left hand side menu for that App.

- It will show you the list of users with the permissions checkboxes. You can manage the permission for users from here.

You can also set the permission for the Apps from the Install Apps option.

- Click on the Install Apps.

- Click on the pack(customer management for QB) under the Installed packs. 

- It will list all the apps under that pack. You can click on any App and change the desired permission for any user in that account from there.

For now, you can not set the permissions at section and object level. But we can take it as a feedback for future development.

-Inder

I understand that we can control permissions at the app level and eventually screen level.

My question is how would you handle a situation where you might want to add a button on a time entry screen called save and approve, but you only want admin level to be able to view and use the button

Hello Mahlon,

As mentioned earlier in the post, at this point you can not set permissions at an object level. I have already pass this feedback to our product team for future development.

-Inder

Can you confirm that permissions at the object level is on the roadmap? Otherwise, how would you handle scenario I mentioned?

Hello Mahlon,

You can achieve this scenario by editing your custom app, go to Rights section and click on Approve and enable it, save the Rights and move to Permissions section and and enable the Approve permission for Admin.

In this way, we can customize this to the user who has Approve permission can see the Save button. 

On your custom app, edit the screen and make the Save button hidden by default. Then assign action on screen load: 

Add check permission action and look for approve permission then add action show/hide control and show Save button.

-Inder

Thanks!

Hi Mahlon,

Permissions (and rights) were a work in progress during the time this initial revision of the Customization 101 doc was written. Rather than leaving permissions out completely we wrote a very high level intro with intentions of coming back to fill in the gaps. :)

Thanks for the posts on this topic!