Feature Requests

Having more issues with the lack of permission controls in SmartSuite. As we are unable to assign tasks to teams and it's impossible to expect people to manually assign several people to every tasks as it's created we have the situation where we are trying to control who can edit what records by locking down the views to specific projects. However, the power search option can't be switched off and I've just found out people have been editing the wrong records for the wrong records. SmartSuite really need to take a look at the overall way permissions are managed and get a workable solution for project management but in the meantime we need a way to switch off the power search option for users.

I end up having to set a lot of people as "solution managers" because I need them to be able to edit all content, not just theirs. But this permission level is too high. They are wrecking havoc on the system because I can't hide fields from them, can't lock them out of editing specific fields and can't keep them from creating new fields. Solution managers end up overwriting fields that are locked down from all other users and should not be editable AT ALL (like "original budget" or "original closing date".... fields similar to a "date record created date" that should not be editable by anyone....) Solution managers end up creating data fields that already exist on other tables that they should be looking up to.... but since they are just in their one department, they don't know about it. For example, I had the solution manager for the "contacts" solution add a field for which floorplan they are buying... but that information lives in the "jobs/projects" solution and should be looked up. Solution managers are creating automations that conflict with or duplicate automations in other solutions. I need to be able to restrict these kinds of things to administrators only... I need solution managers to be able to edit other's information.... but not have full reign to decimate the workflow of the whole company. ;) It would be great to be able to be able to set exactly what each permission level can and can't do.

Enterprises like Gillette Children's need a way to label records by sensitivity (e.g., Internal, NDA, HR Confidential) and automatically manage view/edit permissions without relying on automations. Today, access control workarounds using automations and lookups are fragile, hard to scale, and introduce compliance risks — especially as user counts grow into the thousands. Why This Matters: Centralize all projects in one table, avoiding system fragmentation. Ensure real-time, secure access control without automation dependency. Support sensitive workflows like contract management, litigation tracking, and HR operations. Meet enterprise compliance needs (HIPAA, legal, audit readiness). Requested Capabilities: Assign sensitivity levels to individual records (e.g., Internal, NDA, Legal Only). Dynamically adjust access based on user roles, departments, or assignments. Revoke access immediately when users are deprovisioned. Maintain seamless reporting and collaboration across the organization.

We would like the ability to create our own custom roles that can be linked to users when using the Advanced Permissions option in a solution. We would like the ability to enter a name and description and also select the specific read, write,update and delete permissions. In addition we need the ability to control access to specific records using the Assigned To field. The newly created role should then be displayed in the Advanced Permission Role Selection menu. Please note that products like Stacker and Bubble provide this type of capability and it is very useful.

Roles & Permissions: Support limited admin role - manage users / teams Consider supporting RBAC granularity across admin functions: Authentication / authorization User management Workspace settings Billing / Plan Management Ability to view content*

I love the structure of the Permissions on how application permissions can override solution permissions, and also noticed permissions on the field level are coming soon. Checked for "permissions on the view level" in the community, YouTube and checked if possible in the tool, and couldn't find it. For example, I have the work logs of my staff in an app, where I need to share different views with different people. Will hide the "rate" column, and share it with the project manager, need to share the dashboard view with the client, and so on... Is it possible SS is considering this case or is this topic already discussed in the community? super thanks!

I need to add (many) external users to interact with specific, limited-functionality Dashbaords ... a portal. Back on Sept. 18, 2024, in the "What's New in SmartSuite: Next Generation Dashboards" Youtube video, Jon Darbyshire said the following (at 1:04:57): "We’re going to have a new role coming towards the end of the 4th quarter that we’ll announce more in the next couple of weeks that will be a hybrid (role), that will allow you to give access to certain information in a single instance, maybe to a single dashboard for a much reduced cost. ... It will eliminate the need for you to think about external portals if you want to keep everybody in the context of your authentication inside of Smartsuite … paid for differently." It's now March, 2025 and there's no sign of this. There's not even an entry for it in the Roadmap / Feature Requests (that I can find). Is this still coming?

I would like give employees permission to view and even edit certain apps but not be able to export the data (confidential tax information of clients). Could you provide a data export restriction with app permissions?

Please add feature where permission to Add, Edit teams (everything under Workspace Administration / Manage Teams tab) can be given to a non-administrator account. Solution Creator might (well, I am actually willing to) create solution with multiple "assigned to" fields (think of it as RACI w/ automated status tracking) where each field would have team based member filter to cut the clutter (org of 200+ users). In these cases administrator could consider and give permission for e.g. Solution Creators to form Teams themselves.

It would be useful to be able to bulk update the fields permissions