OK, a quick course in Windows and Access permissions. Since AC2003, DB-level user access control has been discontinued. Therefore, there are only two major ways to achieve the effect you are seeing.
1. IF you have a switchboard or dispatcher form that loads initially and examines information about the current user, that form can assert various control settings to limit or outright block access to certain options. IF there is no such form, then the problem has to be related to Windows file permissions, which can also control accessibility.
2. Windows file settings must be "MODIFY" for the database files AND for the folders in which those database files are stored. "MODIFY" is the broad-brush setting, of which there are only a few. The advanced/detailed settings are 22 in number. These will affect the entire file in that all objects will probably exhibit the same behavior. I.e. can change one? Then can change all. Cannot change one? Then probably cannot change any. The permissions of a given user can be determined easily enough.
For a given user that you wish to evaluate: Using Windows File Explorer window, find the folder containing the Front-End file. (Might also need to find the Back-End file, depending on specifics.) Found that file? Then...
1. Right-click the file to expose the drop-down list.
2. Select Properties >> Security
3. Select Advanced
4. In the list that shows up, find the username and look at the permission for that file
You may have to repeat this process for each user and each file that is part of the database. All database files and the folders they are in MUST have at least MODIFY permissions. There is also the matter that the TRUST CENTER might see those two folders differently.