App Level Permissions
Is there a way to set app level or form item level permissions in a space?
Please sign in to leave a comment.
Is there a plan to add permissions at the app level as well?
Hi Alycia - no plans for this. We are keeping access at the workspace level for now.
/Jacquelyn - Podio
Hi, this looks me quite big qustion, where is applicable podio. exactly understand, idea of podio is very fresh interesting (reason, why i'm interested on it)
Consider: other solutions to help business companies has security on the next levels, please tell me how podio want to face bellow requirements if facing on implementation.
- module (group of databases)
- database level (it's mean app in podio)
- record level (so somebody is part of an area but dont want to show him number of records - i.e. group east sales team not privileged to see leads of west team)
- fields level permission - some users should be are not entitled to see some fields - i.e. company in database has turnover and not possible to see this field - i.e. group of roles
- Role Based permission - should group rules and security policies.
Our real customer scenario, where we implemented a CRM solution: Customer 70 salesmens, 5 continents, 12 countries. Company has strong sales team with a big pipeline reported from sales opportunities database, and salesmens are grouped to security groups. i.e. Gulf Sales Team, HK sales team, LA...etc. Because company products is a creative product designed based on collected requirements, PM lead the project, and designers are design mockups, then manufacturing realise and implement.
The applied security was sm should create/edit own records, read only group records (i.e. LA team), but tho whole word should see opportunity records as list, but cant open see details and volume. PM's own Project recors and portfolio, but cant see value of business and sales cant see purchase costs...etc. It was realised by SugarCRM Community edition. Each Project has own workspace for realisation, shure in DMS/ECM.
So tell us how we should solve the above scenario. If i create for each team own workspace - then i need 12 CRM workspace. and drop the simple repors as dashlets and sync data - write API - and/or send data to external ETL tool for consolidation or consolidate manually data in 12 xls sheets each day......
The most important think why i'm dealing with podio is drop too many apps, which are organised in schilo, BUT other hand because some business practices are not implemented in this beatiful product, then must create complicated structures.
It's about positioning, i know the price is good, i like if podio consider and/or ask business consultants about real requirements. Competence not sleeping, and should be wrong to lost big opportunity to make world email-less ;)
what, you and other thinks ?
@Norbert Bede, exactly! I am in the exact same boat as you - I have the same requirements. Right now, my workarounds aren't working = too many workspaces, no auto synchronization, all-or-nothing permissions, not admin control over access levels, nothing that avoids duplicate entries, and no global dashboard view that allows the PM to quickly see what projects/workspaces are at risk.
Otherwise, Podio has enormous potential, and sure is pretty.
I DO LOVE Podio's rapid task entry that enables me to make a new task from anywhere by clicking "T." This is why I refuse to replace Podio's native Tasks feature with a custom App to handle project tasks, because making tasks via apps becomes too cumbersome.
I wish Podio would invite real-life external project managers and serious business users, like you, to their development collaboration round-table meetings. This way, the guest contributors could raise concerns and offer input on Podio Team's ideas, in real-time. I realize that Team Podio believes they are already doing this - factoring in user input via these forums - but there is no one inside the team meetings who can openly critique new feature concepts as they are being discussed; not just after release.
There is great risk to product and service development teams who work in silos where everyone is in love and in agreement with each others' ideas. There has to be conflicting points of view at the table in order for real progress to be made.
I hope the Podio team realizes that most of us love and admire Podio enough to invest our time talking about it it forums like this one; rather than taking our concerns and complaints elsewhere - review sites. I think we all really want to believe that Podio will mature to suit our needs. In the meantime, we are left taking a wait-and-see approach.
Summer makes a very good point here. It's hard to see the Podio team's development priorities when new features often pop up unannounced and are sometimes unrelated to us users' needs. For example, we are very glad to have 'live' commenting but essential features such as contact management have been <a href="https://help.podio.com/entries/21663348-workspace-members-and-workspace-contacts">problematic for a while...</a>
And I do understand the need to add shiny features and maintain secrecy in a field where there is quite some competition, but we have chosen to side with Podio and we believe in its potential. Organizing some sort of consultation and taking feedback on your development priorities are two simple ways you could keep us involved and make us feel the software is evolving in the direction we need, and not with other priorities in mind. Thanks!
Hey Laurent, our CTO Phil Chambers comments on this thread: https://help.podio.com/entries/21724222-How-do-I-delete-many-line-items-at-once-.
See attached screenshot if you don't have the stamina to scroll (it's quite a long thread) :)
The release Phil is mentioning is the live comments one, but look out for new stuff soon.
/Gustav - Podio
This is music to my ears, thanks Gustav! We're hoping to see functionality boosts.
Just wanted to mention that in terms of community information and involvement, forums are one of the worst options because everything is related to a thread, and as you see here and there many people have very basic, core issues with Podio that go beyond any single feature.
As it has been mentioned elsewhere, a roadmap of sorts would allow us to plan ahead and not apply workaround modifications to our apps or workspaces for something that will change within a year - for example, without app-level permissions my workspaces are becoming complex because I have sensitive information in some apps and in the same space very public info (contacts, etc.) that demands wide access.
Anyway, keep up the good work!