Even though permissions related to resources enable you to carry out certain actions regarding your own resources, you need specific permissions over resources created by others. This is achieved by assigning resources to a role. Both default and custom roles can be given access to Devo applications, Activeboards, alerts, and lookups.
Public resources in your domain will appear listed in their corresponding tab and you can make them available to roles with specific permissions. These permission will dictate the area of the app as well as the kind of action the role can perform, while assigning a resource will dictate the specific resource you can interact with.
Permissions-resource interaction
The ability to perform actions related to resources depends on this combination of permissions and resources:
Assigning permissions without assigning resources will only grant theoretical abilities with no actual resource to work with (see Role permissions to know more about the actions each level involve).
Assigning only resources without permissions is not allowed (the tab will be disabled unless you have at least the view level of the corresponding permission).
The permission level determines the maximum scope of action for the resource. For example, if you set the permissions to view, you cannot assign the resource to manage. However, if you set the permissions to manage, you can choose that a specific resource is set to view.
Make resources available to assign
Tabs will appear empty until you create a resource in the corresponding area and share it. Check the following articles to learn how to share those resources that require it: Sharing Activeboards, Share lookups.