KLASH has a few different Roles for you to use when you need to control what Users can and can’t do. Here is an overview.
Can only look at things and write comments. This is almost the same as using Share links, but with a Viewer account the person you want to collaborate with can be given access to one or more of your Projects. They will receive mentions and other activity, and if you later on decide to promote your collaborator to allow uploading, you can just change their Role to Member.
A common use-case for the Viewer Role is collecting feedback from people who only have a reviewing function in your team, i.e. that don’t need to contribute assets. The role can also come in handy when you need to invite someone from outside your organisation, e.g. a client, but you don’t want that person to be able to make any changes to your resources.
The bread and butter Role of most teams. A Member can do pretty much everything, short of managing Project and Team structures and Company settings. All asset management, collaboration and share features are available to Members.
The Admin sits at the top of the permissions hierarchy. They can do everything. What sets the Admin Role apart for the others is its permissions to manage Project, Team and Company settings. This includes creating new Teams and manage Team memberships. If you are on an Enterprise plan, your Admins can invite new Users to your Company, manage integrations and configure Verified Domains.
How you distribute Admin Roles is up to you, Klash is not opinionated on this topic. For some organisations it makes sense to make everyone an Admin to avoid bottlenecks, where as others might have requirements to restrict these permissions to a smaller group of people.