Larry Baxter
ยทSolution and Process Developer/Consultant

Limiting Visibility on a Tasks Table

I'm looking to have a basic Tasks app for about 50 people spread among 10 teams.
Rather than a separate Projects app, just use a Multiselect field to group tasks in a project.
I was hoping to allow all users to freely create (and view/edit) tasks for themselves while letting Team Leaders view (but not edit) all tasks. First thought was to use Advanced Permissions. Editor access should work fine for Team leaders, but I don't see any permission type that can create new tasks without also allowing them to view all records in the app. The closest seems to be
Contributor "Contributors can view and create records, but can only edit existing records when they are included in an Assigned To field in the record." Seems like they can view all?

* Am I misreading the Contributor role or is there another role that works as desired?
* Is the best practice to instead just let everybody see every record in the Solution?
* Or is to to have 10 virtually duplicate apps for 10 teams? (I would sure think not!)
* Bad idea to use a Multiselect for simplified grouping of tasks into projects with a large # of people as that list might get unwieldy?
* To encourage users to work on both personal tasks and assigned work tasks, do
you have just the assigned tasks all visible in an App and point them to "My Work" to
add their own personal tasks?

Bottom line: I'm looking for a way to let a few dozen users create their own mini-projects and tasks that they and their supervisors can see, but others can't. Any feedback is welcome, thanks!

2
2 replies