This looks like a very similar question. Take a look at @brasofilo’s answer, you can modify for your own needs.
There are a couple of ways you could approach this: you could set up a custom role for your client’s user accounts, giving them all the rights of an admin. Add a capability to the main admin role ($role = get_role("admin"); $role->add_cap("edit_acf_fields",)), then using these hooks to check for that role and deny access.
$current_user = get_current_user();
// If the user doesn't have the capability, no editing ACF settings.
if ( !$current_user->has_cap("edit_acf_fields") {
// hide the menus
// or kill the screens
}
The main reason to do this is portability. You (or the client) might want someone else to work on their site one day, they’ll need their own account. More complex, but the recommended solution.
Alternatively, you can just check for your own email address and call it a day:
$current_user = get_current_user();
if ( $current_user->user_email == "[email protected]" ) {
// hide the menus
// or kill the screens
}
This is essentially invoking magic numbers, as an editing screen appears or disappears based on who you are, and there’s no obvious explanation or way to change that behavior to the user. Easy, but Not Recommended.