The first question is how many actual users? If 20 or less, Access is a very good solution. Up to 50, Access could be fine if they are not always using it. Otherwise you could need SQL server or something similar. Even so, Access would be a good place to start your database and application design.
You don't indicate your level of Access experience. VBA is vital to include access control for each user. Although you can use Access's security, I prefer to write a log in screen to the application and use a table listing users, passwords, ID, user group, etc. In the application define a module with some public variables, including strUserID to capture the ID of the logged in user. On various menus, forms, and queries, use strUserID tocontrol the visible property of various controls to true where you only want certain users (or groups of users) to have access to various functions and/or data.
Forms containing data which only the logged in user should see ("personal data") should run from queries that include the selector that UserID = strUserID so only that person's data is visible. Ex: diary, daily accounts. You can also use strUserID to limit the data that can be changed to only that user's data, even if other users' data is visible. (For example, when scheduling meetings.)
Remember to keep the back end (data tables) in a separate Access database from the front end (application-forms, reports, modules, queries, etc.) for ease of development & maintenance. The users should only see a menu driven application and not see the database window or be able change designs of forms, etc.
Hopefully this will at least help you get started.