Hi @JakeYL26 The reason a standard user can see everything is when they are in the same group and/or company as the projects. Like I said, I would create a group just for these external people. Then share those few projects only with that group.  

@Doug_Den_Hoed__AtAppStore I was thinking about that approach with calc'd fields and it made my head hurt   I like your idea of using approval paths - but I think @rebeccabirkholz47 wanted to track the process step of the artist (since approvals may take a while). That's why I thought in her case th...

On the project page:  

Only by way of sharing those specific projects with that company.

Hi @rebeccabirkholz47 I was going to suggest a task report and filter wherestatus = With Account Services previousStatus = New hours = zero But those are the total task hours.If you need to check whether the artist logged hours "while in New and before With Account Services" I think you'll need Fusi...

Yup. I suggest a group because then you can add/remove users from that group without having to remember the person(s) that should get the access.  AccessLevels is a good call to dial in what exactly the person should be able to do - once the can access an object. Finally, you may want to use a layou...

Hi @DestPr Thank you for that! Sadly I have more questions  So if I understand correctly the first iterator loops over the list of suffixes from the tools module? I can't tell what #4 is - Create Product Combination? Some more questions & comments: label your modules - makes flow understandable to s...

Hi @TammyCa1 You could run task report or an assignment report - if those tasks can have multiple users, you likely want the assignment report. You can then group by user. As a filter you compare actual vs planned completion date: Task reportactualCompletionDate=FIELD:plannedCompletionDate actualCom...

Hi @JakeYL26 I would look at using groups first. E.g. create a group for this user, and share with this group what the user can access.

Hi @skyehansen Per APIexplorer there is a linking object "ProjectUserRole" (PTEAM) that has projectID and roleID attributes, but I'm failing to make an EXISTS filter work - what am I doing wrong?EXISTS:b:$$EXISTSMOD=NOTEXISTS EXISTS:b:$$OBJCODE=PTEAM EXISTS:b:projectID=FIELD:ID EXISTS:b:roleID=64d51...