I don't see anything from your post that would be a problem
Maybe it's not really a problem, but one db for each project should be a no-go. It's one for one and one for all. Also, One Drive for using Access is a non-starter. If you need remote access to the db, there are other ways but not that one. It's a sure-fired recipe for corruption and introduces a requirement to sync data if more than one person can simultaneously use the db.
As noted, Access has a large learning curve but it is quite robust in what you can do. How easy it is made for everyone to use is the responsibility of the designer. I have built Access databases for contracting (on-site and off-site) and was a coordinator for both aspects in the latter part of my career so I might know a bit about what's ahead of you but certainly not enough to know all the specifics of your operation.
If you want a flavour of how Access is different, start by studying database normalization.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.