Showing ideas with label permissions.
Show all ideas
Status:
New Ideas
Submitted on
‎Apr 06, 2024
07:17 PM
Submitted by
AlyWEV
on
‎Apr 06, 2024
07:17 PM

I created an interface that pulls from one table in my Base. With some of the demos I've seen on how interfaces can be used, I thought this would be a great way to display non-sensitive data via a public share link. Other tables in this base, however, do contain PII and cannot be shared with the public. So, after creating a lovely interface that seemed it would do exactly what was desired, I tried to share and found that I can only share with individuals who are signed in and have access to the base. Chat support let me know that the Base's permissions determine the interface's share permissions. In my specific use case, I have a base that shows all the volunteers that work with my organization, including a table for their basic contact info, a table for their engagements with us, a table for touchpoints we have with them, and another table that holds all the categories of expertise for our volunteers. The interface is based on this last table, and is a record review that tallies the number of available volunteers with each area of expertise. The data on that table is fine to share publicly, but not data from the others. Ideally, when building an interface you could choose how to share the individual interface without the whole base being set to public. Anyone with ideas of workarounds, I'm all ears!
... View more
Status:
New Ideas
Submitted on
‎Mar 15, 2024
05:16 AM
Submitted by
tomo
on
‎Mar 15, 2024
05:16 AM

Option to Limit the Access to Interfaces. I want to build an App for my co-workers that are not that techie. So i want to keep them from seeing the Base and only allow them to see certain areas of an Interface. Would be helpful for customers too. Sadly there is no way, as far as i can see
... View more
Status:
New Ideas
Submitted on
‎Jan 04, 2024
07:29 AM
Submitted by
MichaelSargent
on
‎Jan 04, 2024
07:29 AM

I manage one base with two interfaces for my company. One is the Team interface everyone has access to and the other is a Management interface where only management has access to. The Team interface undergoes the most evolution and it's nearly impossible for me to keep open record panels consistent across both interfaces. Frankly, I find it ridiculous you can't copy open record panels from another interface that shares the same base but that's another point entirely. Ideally, I would like consolidate both interfaces into the Team interface and the Management pages have a password protection feature that prompts you to fill in a password (one singular password specified in the interface editor - no need for separate user passwords) before permitting access to the page. The current system makes it difficult to scale and retain consistency across multiple interfaces and I feel like this would be a simple solution with a big impact on permissions.
... View more
Status:
New Ideas
Submitted on
‎Jul 07, 2023
06:17 AM
Submitted by
Sean_Murphy1
on
‎Jul 07, 2023
06:17 AM

What is the proposed idea/solution? Not really 'row locking' in the database sense of dealing with simultaneous access, but rather the ability to mark a record as immutable or set certain permissions for it. Additionally -- and critically -- the ability to trigger this function through Automations. How does it solve the user problems? Enhance control over data integrity by preventing accidental modifications once a record is 'complete'; Streamline certain workflows by marking task completion; Ensure that only the right people are able to edit a record at certain points in its lifecycle, with changes to the permissions triggered by Automation, and; enable customization of data access on a per-record basis. How was this validated? User feedback expressing the desire for greater control over record modifications (which can sometimes be addressed at the Interface level with the 'Current User' option in filters, but it's not appropriate in every case and only applies to that one interface) and to prevent modifications to complete records while still being able to read the ticket in all of the normal ways (no easy way to do that from what I can tell.) Who is the target audience? Teams & Organizations managing complex workflows; Data Managers responsible for maintaining data integrity, and; Consultants & Agencies setting up systems on Airtable for their clients. This addition would bolster control over data modifications.
... View more
Status:
New Ideas
Submitted on
‎Jun 21, 2023
08:17 PM
Submitted by
Petrowatch
on
‎Jun 21, 2023
08:17 PM

What is the proposed idea/solution? We need to have security features for the mobile app. 2FA, Fingerprint, maybe a secondary profile that the "Admin" can accept or deny changes. Its just too open. Double edged sword. I'm happy it exists and works for my use case but what if someone steals my phone, or a sibling's using my device opens airtable and starts deleting sht! How was this validated? You're the engineers and UX designers... you tell me. Who is the target audience? Everyone who uses the Mobile app and cares about the integrity/ security of the data
... View more
Status:
New Ideas
Submitted on
‎Jun 06, 2023
05:53 AM
Submitted by
Cynthia_Sanchez
on
‎Jun 06, 2023
05:53 AM

What is the proposed idea/solution? From the Admin panel, to have an option that disabled everyone that is not an admin from creating new Workspaces. How does is solve the user problems? The issue is that users in our organization create new workspaces, and this turns them into Owners automatically. Then, they are enabled to share access and provision higher licenses to other users, changing our billing. We have documented this issue internally, but our company has hundreds of users on Airtable. Employees join and leave the organization every month, meaning that it becomes unviable to rely merely on internal training. The tool needs to enable admins to protect the billing cycle. How was this validated? We see the issue every other month. Who is the target audience? Enterprise accounts
... View more
Status:
New Ideas
Submitted on
‎May 18, 2023
12:45 PM
Submitted by
filipradkiewicz
on
‎May 18, 2023
12:45 PM

What is the proposed idea/solution? The proposal is to abolish the fees for Interface-only commentor level. Actually, a commentor is a viewer with the possibility to comment, nothing beyond that. No edits, no creation, no management, etc. How does is solve the user problems? It would change how companies (like my agency) can communicate with their clients (specifically those who are not active on a daily basis) or external partners over e.g. the workflow, reducing e-mails or calls. Clients (free of fees) can add records to a base via forms and can read them on Interface, but there is no chance to leave a comment.
... View more
Status:
New Ideas
Submitted on
‎Apr 04, 2023
07:43 PM
Submitted by
D_Gauld
on
‎Apr 04, 2023
07:43 PM

What is the proposed idea/solution? Add passcode lock feature/option for iOS App How does is solve the user problems? Airtable stores a vast amount of data which may at time be confidential or require additional security. Viewing of that data by persons other than intended could have detrimental consequencee. How was this validated? There is no lock feature in the app. Who is the target audience? Anyone who uses the mobile app.
... View more
Status:
New Ideas
Submitted on
‎Mar 22, 2023
12:11 PM
Submitted by
giulia_mg
on
‎Mar 22, 2023
12:11 PM

This feature would be useful for businesses and organizations that need to temporarily disable form submissions for maintenance, during periods of high traffic or when responses can not be accepted due to a specific workfloy/company necessity. Here's how this feature might work: First, the user would need to create a new form or select an existing form within Airtable. Then, they could choose to enable the form scheduling feature for that form. Next, the user would be able to specify the start and end dates and times during which the form should be disabled. The user would also have the option to add a custom message that would be displayed to users who try to access the form during the disabled period. For example, the message might say "We apologize for the inconvenience, but this form is temporarily unavailable. Please check back after [end date and time]." After the disabled period has ended, the form would automatically become active again and users would be able to access and submit it as usual. This feature would be especially useful for businesses and organizations that need to periodically disable form submissions for maintenance or during busy periods, such as holiday sales or seasonal promotions. By giving users more control over when and how forms are displayed, Airtable would help ensure a smoother and more efficient workflow.
... View more
Status:
New Ideas
Submitted on
‎Mar 22, 2023
11:40 AM
Submitted by
giulia_mg
on
‎Mar 22, 2023
11:40 AM

One potential Airtable product idea could be the addition of a feature that allows for the enabling or disabling of column visibility for individual users or groups of users. This would be especially useful for teams or organizations that work with sensitive or confidential information, as it would give them more control over who can view certain types of data without having to create various views/tables/bases for each user. The same way we can choose who can edit a collumn, we could choose who can see it. Here's how this feature might work: First, the user would need to create a new table or select an existing table within Airtable. Then, they could choose to enable the column visibility feature for that table. Next, they would need to select which columns should be visible by default, and which columns should be hidden by default. Finally, the user would be able to specify which users or groups of users should have access to certain columns. For example, they might choose to hide certain columns from all users except for members of the finance team. This feature would be especially useful for businesses and organizations that need to keep certain types of information private, such as financial data or customer information. By giving users more control over who can see certain columns, Airtable would help ensure that sensitive data is only viewed by authorized personnel.
... View more