 | Philipp Matuschka (MMB) 8/16/2011 7:42:58 AM Can I suggest creating a setup permission called "report writer". Users with this permission could
- create new reports
- see and copy existing reports, thus creating a new one
- edit or delete reports created by themselves
- manage view subscriptions for reports whgich they created
I am finding that this is a task which could be delegated to "superusers" as opposed to developers, but because of the way the permissions are organised I would end up giving these superusers access to everything which neither I nor they want.
Thanks
|
 | Rebecca Sell 2/2/2020 2:34:11 AM I’m sure I asked for this about 3 years ago ?!
|
 | Michael Clay 3/30/2020 1:22:48 PM Not only views/reports but also email notifications/reminders and documents. A person with access to data and users should be able to create their own email reminders and documents as those can vary with time and taste. I would like the users to be a little more independent as long as they can't change the database structure. It is silly that the database creator/developer, usually just one person, is the only one that can create those kind of things. If someone hires another to create their database they should not have to pay them to create views, email notifications, and documents.
|
 | Rhyno du Plessis 1/20/2025 8:57:30 AM We would also love to have this functionality.
In general, it would be great if we could have a setup read-only role by allowing access to the setup but turning off modification rights for columns/views/etc.
|
 | Luison Lassala 3/4/2025 5:46:24 AM This idea request is a must - it is very costly for us developers having to attend to every single little request from end-users for modifications on Views (modify the filter or sorting option, add new columns to the view, colorize the rows, etc). After proper training, end-users (or some super-users) should have permission to make changes to some configurations of the database but not to others.
Other platforms (e.g. Salesforce) allow for more 'granular' permissions in Setup. TeamDesk only allows 4 options: Full Setup, Data Only, Users Only, Data & Users.
There should be at least three more options: Configure Views, Configure Documents, Configure Email Workflow Actions.
|
 | Nick Ashcroft 3/4/2025 8:25:14 AM going one step further, it would be nice if the user could create/manage their 'own' views that were visible only to them, rather than be able to manage all (global) database views
|
 | basenine 4/18/2025 10:51:15 PM **End User Access for 3rd-Party Accounts only rather than full access
|
 | Jorge Solá 10/28/2025 5:18:15 AM As a stopgap measure to allow users with no setup access to import data into the database, I've developed an IMPORT DATA table with a Text Multi-line column where regular users can paste a spreadsheet range that they would like to import. The data is then parsed & turned into individual records in their table of choice. If you are interested in this solution, please contact me & I can provide details.
|
 | Kevin Alberts 10/28/2025 11:34:03 AM Hey Jorge,
that workaround sounds really interesting — thanks for sharing!
I’d definitely like to know more about how your Import Data table works and how the data gets parsed into the target tables — sounds like a clever solution.
At the same time, it would be amazing if TeamDesk could eventually allow non-admin users to use the regular “Import data into table” feature, but with limited permissions — for example, import access only for specific tables, without setup or delete rights.
That would make things a lot easier and safer for many setups. 🙌
|
 | L. C. Parker 10/28/2025 11:36:28 AM @Jorge Solá: I am *very* interested to hear how you did this. Nice work! Love to hear about the problem solving.
|
| Jorge Solá 10/28/2025 11:58:23 AM You can write me jsolaullod@gmail.com or call me: +34 644 479 831 (I use WhatsApp as well).
|
 | Shaun Lamminga 10/29/2025 2:19:01 AM We get around this using a simple piece of html and javascript that ingests a sheet (csv or xlsx), converts it to JSON, performs "fuzzy-finding" on references to ensure the "Ids" are used where required (Even if they spell it wrong in the sheet). The script then uses the users credentials to post into the table of choice through the API. I believe writing an import tool like this gives you the most control.
|
| Luison Lassala 10/29/2025 3:38:49 AM Hi Shaun, that sounds interesting... Would you be willing to share the HTML & JS code?
|
 | Slava Shinderov 12/18/2025 3:01:00 PM Merged with:
449 - Setup permission - report writer
|
| Slava Shinderov 12/19/2025 6:19:36 AM @All we’ve changed how setup permissions are configured.
From now on, you have the following options: “No Access”, “Full Access”, and “Restricted Access”.
For “Restricted Access”, you can specify the following permissions:
* Manage Users
* Manage Data
* Manage Views
* Manage Documents
* Manage Forms
* Manage Dashboards
* Manage E-mail Notifications
Moreover, when “Restricted Access” is selected, the user will only see the tables that are accessible under their role.
|
| Luison Lassala 12/19/2025 8:59:03 AM Wonderful!!!! Thank you for listening and delivering this request - it is going to make life so much easier for us db developers!!
|
