Great input, thanks for sharing guys!
//Sara - Podio
There should be a way to lock individual fields in an app! It would be nice if we could do that! That would really make Podio flexible.
Great input, thanks for sharing guys!
//Sara - Podio
Please sign in to leave a comment.
I agree! We should be able to lock individual fields so our members/user won't be able to change some fields but able to change other fields.
For example user should be able to change "Date" fileds and "Status" fileds, but not "Relationship" fileds, because sometimes thats for internal administration purposes and needs NOT to be touched by a hired freelancer or subcontractor or even internal members such as Sales Reps etc.. However the Date field should be able to be modified by such people.
Thanks for sharing your idea!
Can I ask if you already use the Item Activity to view and revert changes?
Do you experience this problem often (members changing fields they shouldn't)?
Would be cool to hear your experience more in detail so we can learn from it :)
//Sara - Podio
We hire freelancer to help us with Web Design projects and we paid them based on Deliverables that they complete. We have created an App called Deliverables, when a Freelancer finishes a job we mark the deliverable complete, however sometimes the Freelancer jumps the gun and marks the deliverable complete on his own so we always tell them not to touch that particular field but sometime they forget, so than it takes us lots of micro managing by keeping and eye on Item Activity to view and revert changes. We have 1000s of deliverables and 10s of freelancer so you can imagine that this creates lots of work for us just to make sure that freelancer touch the fileds they need to and NOT touch fileds that they dont need to. We have to train them on how to use our Podio Deliverable protocols raising the cost of our staff training. All this could be avoided simply by having a feature were we could lock certain Podio filed so they cant be changed and leaving open other fields. Now this is just one example but we do have other situations that this feature could help majorly. I just dont have the time to mention all of them :)
Hi, I also miss this possibility sometimes, but it's more to prevent unaccidental changes. Categories - which you just have to click - and other text fields happens to be changed sometimes, which I think is just by mistakes, since it just takes a click.
One solution would be to have the option for each field - or for an entire item - to protect them by an "Unlock to make changes" option, so you have to click a lock before it is possible to edit that specific field or item, like before when you had to select "Edit item", before you could edit an item.
I can see there is an option about "members can't edit" for apps. Can you please explain this, since this might have some relation to this.
I really need this function as well! Just add a padlock symbol or something at the end of the field so it can be locked and unlocked
I'd like to use it for my staff to register times, and then an admin can OK the registration.
I also agree that this option would be very helpful as there are certain things which are way too easy to change, especially options within relationship fields - sometimes they get changed and the person doesn't realize that it is changing it within the whole app, not just within that single item and there are way too many things to keep track of to try and monitor that! At the very least, once information is entered initially and an item has been created, it should require confirmation to accept changes if you are editing that item or clicking on something to indicate that you are consciously choosing to edit the entry rather than having it be something that can be done without even realizing it, then you click off the entry and it saves your changes without you ever realizing you made changes!
Here's a use-case for this:
We have certain fields that the admin and project manager set up in the very beginning for the team to use for the duration of the project (we use a workspace for each project). For example, we have a Roles app that has a dozen or so standard roles - 7-12 of which are used, depending on the size of the project. As the admin, when the project kicks off, I set up a new workspace based on a templatized version of our project workspace, and I copy the 12 roles into the roles app (they exist as a drop down list of categories in the Roles app). Each role has its own description and relationships to other items (like Key Milestones), for which those roles are responsible or to which they contribute. Then they can assign a role to a team member logged in the Team app (sometimes people are assigned to multiple roles on a project, and their role varies from project to project). This is a great reference for folks to know what they're responsible for as soon as the project kicks off.
Unfortunately, the project manager (if they're new) can very easily accidentally change the role title field to a different role title (say, for instance, if they think they want to assign the team member linked to the role to a different role) - now, unless I catch it, the description and all the relationships in the role are wrong. Then the project manager gets confused and adds a new role to the app, creating a duplicate record with none of the relationships and relevant information. If I had the ability to lock specific fields so that these couldn't be changed after they're setup, it would make my system waaaaay safer for folks to use.
Any update on this issue?
This would be awesome for us as well. We do federal work and to be able to "lock" fields and even app items once they are "completed" would be perfect in case we get audited. I know we can do a "roll-back" through Globiflow but a lock function would be much better.
Locking based on a field update (like a status or completed date field), locking based on a sign-off field, or even locking based on X number of days after a specific field has been updated to allow for everyone to have their data in.
Is there any update on this? We could really use this feature for many of the above-stated reasons.
Really need this.
I use PODIO to coordinate the volunteers that are going to be in a consultation. All volunteers have access to PODIO. Their only task is to put their name in the "volunteer" item but the ones that are less confortable with technology just start to change everything. We train everyone but there is always someone that changes items that shouldn't be change, like dates, names, etc. To revert changes is a daily task. SO this would be a really awesome addition to PODIO.
Would be very beneficial! +1
Yes, this would be very desirable. Creating office procedures using an app from the store for this purpose. Dont want team members editing the procedures and processes randomly. So, due to lack of this feature, have to put the procedure into a pdf file and upload to Podio. Silly that we cant put it in the text field and just lock it from editing.
You could accomplish this using globiflow to revert that field to the previous version when changed.