Generally speaking I would say yes. But there are several factors that will drive the decision of having a single app or multiple apps. When you mentioned you expect upwards of 80 Actions in the app, that is a signal to me that the app is very large or very complex or both and a prime candidate for multiple apps.
Let’s assume you have a group of people responsible for planning and scheduling projects as well as maintaining a backlog of projects. They typically do not care about the daily progression of the active projects. They really only need to know what status active projects are in so that they can plan for release of the next project.
Managers, supervisors and employees actively working the projects don’t really care about the daily management of the company-wide backlog, planning and scheduling of projects. They do probably want to know scheduled projects coming their way soon and have a smaller need to manage those!
So, I would create at least two separate apps Project Planning and Project Execution. Each app has mostly self contained data with only a slight overlap.
Then within each app you can apply Security Filters to limit the data to only what each company employee needs to see. For example in the Project Execution app, employees see only projects they are assigned to, supervisors see all the projects for all the employees they supervise and managers see all the projects for all the supervisors they manage, etc.
Similarly, you can turn on/off certain features based on employee roles…such as the Admin and User roles provided in AppSheet OR your own custom set of roles you build.