I have a user who is a manger and want to grant access to the following area so they can continue editing a profile field:
Home / Site administration / Users / Accounts / User profile fields
When the user tries to access the area, they get an access is denied error.
I tried viewing the Define roles for the Manager, but couldn't find the correct one for that page.
Is this even possible?
I am on version 3.6.3.
The user needs the moodle/site:config capability which will give them access to pretty much everything.
You could try creating a new capability or using an existing capability, then editing this line in /admin/settings/users.php
$ADMIN->add('users', new admin_externalpage('profilefields', new lang_string('profilefields','admin'), "$CFG->wwwroot/user/profile/index.php", array('moodle/site:config', 'newcapabilityhere')));
Related
All, I'm unable to add a new user under the Admin > Access & Authorization tab in Google Ad Manager (ex: DFP). (Role > Partner Portal user).
I have this error: Unable to save. Check highlighted errors and try again. Problem is that nothing is highlighted, so I don't know what's wrong.
I'm inviting a third party which has a gmail address, I've also cleared my cache, login/logout. I'm using Chrome, and even tried via my mobile phone (Android/Chrome).
Thanks for your help,
If you are admin then Ad Manager should allow you to add users.Please navigate to Admin > Access & Authority > Users. You may refer to the screenshot attached below.
Now your main problem is that it's not highlighting what's the error. Google Ad Manager is very strict when it comes to permission to access the platform. When you give a general email address such as "example#gmail.com" it won't allow you to add the user. It has to be a registered company email address such as "seb#company.com". In addition, that company should be registered with Google Ad Manager to use their services.
Is there a feature in moodle that allows users (users that have an access, not guest) to enter the course with a link shared by admin?
What I want is that when a user clicks on that link, a login page appears, after logging in, the user is automatically enrolled in that course.
Moodle version: 3.6.2
Without the need of coding, you could enable the self-enrol enrolment method at course level with enrolment key (defaulting to student role), then provide the link to the course to the existing user you wish he/she self-enrolls as student.
The user, once logged in and trying to access the course, will be presented with a form requesting the enrolment key, once the correct key is provided he/she will be self-enrolled as student.
If you want something more direct, like a token based kind of direct authentication+enrol you will need to use an existing plugin (like this one https://moodle.org/plugins/auth_enrolkey) or write your own.
I'm working on JasperReports Server community edition.
I need to configure it so, that after logging in a user can only see specific reports, otherwise s/he should not see any other folder/resource.
As per Jaspers permission Guide, it should work with this solution but does not work somehow.
A new role eg "TEST_ROLE" was created by jasperadmin.
A new user "TEST_USER" was created and the role "TEST_ROLE" was assigned to him/her.
Now for the "TEST_ROLE:
For Repository root, permission No Access was set.
only on specific reports Read onlypermission was granted.
But when TEST_USER logs in, he sees below message:
You do not have permission to view this page.
Please contact your system administrator or log in as a user with permission.
Why it does not work?
Question2:- User with role "TEST_ROLE" should not be able to upgrade his permission. Is it achievable with permission Read only as I have described above?
Question3:- I did not get what's the diffence between Execute only and Read only permissions?. What I could comprehend that user can view/execute self created reports with execute only permissions?
The difference between Execute Only and Read Only is that those resources which have Execute Only cannot be 'seen' by the user but can be executed.
This becomes relevant when reports that the user can see are dependent on other resources in the repository eg datasources, domains, images etc.. .
To run the report the user must also have access to these other resources.
If you want to restrict the user to only to be able to view reports they can run then set the reports to 'Read Only' and set all dependent resources to 'Execute Only' on the relevant role.
This is what is possibly causing the permissions error you are seeing.
I am trying to add a new member on my google-cloud project but i can't make it work.
The link inside the auto-generated email from google is well linking to the page where the user can confirm/decline the invitation inside a modal.
But when this user click "confirm" an error message appear inside the modal but disappear immediately - so quickly i can't read it. As a result i can never grant access to my project to this user.
In my browser debugger here is the error i can trace (some values are forged) :
"NetworkError: 400 Bad Request - https://console.developers.google.com/m/teams/acceptinvitation?xsrf=AFE_nuNg_V8394FDKjdfkjkjwKDFXDVg%3488T6J5783&authuser=1&action=accept&pid=apps~myproject-hosting&receive_updates=false"
This user has a custom domain which is a google-apps managed domain. I specify this because its the only kind of users we cannot invite to the project.
No problem for adding users with #gmail account.
From the google-cloud documentation i can read this :
If you are using a Premier or Google Apps domain, the administrator for your domain should first create the Google account from within the Users panel of your Admin Console.
I don't understand this sentence as my user is off-course already listed in my domain.
This might be expected behavior from the App Engine. I know that once you link you application to a specific domain via Google Apps, it becomes very hard to add people from outside that domain to your application.
I know that you can create a google group, enable "out-of-domain" members to that group. Then you can add that group to your project. Then you can add his email to the group, which should give him access to the project.
Only caveat here is that, if your domain is google.com, you will not be able to use this workaround, and this may require help from support.
Well i finally did it.
Google seems to have fixed the flashing error message making it impossible to read.
Now it display something like this : "Contact your administrator to enable AppHosting admin on your account".
This is done has follow :
Login to your main google-app account on http://admin.google.com
Go to "App"
Go to "Additional Google services"
Enable "Google Developers Console" for everyone
Now my user can be invite to the google-cloud project.
I have an account setup exactly the way I'd like a number of individuals accounts setup and I'd like to create them as clones of this account so the get the initial set of permissions without me having to manually set all the permission on each account.
Note: It is fine (ideal?) if once the accounts are created that they no longer have a relationship with the original account. For instance, if User A is the base account that is being used to create all the other accounts, once User B is made from User A then all further changes on User A will not be reflected on User B.
Any ideas?
In answer to your question: no, there is no clone/copy user feature in the User Editor in Sitecore.
It sounds like you would be better off creating a role with all these permissions, then assigning this role to any new users you create. You could then modify the permissions of the individual users as necessary.
Note this would not be the ideal solution as it's always better to apply security to roles rather than individual users.
Perhaps you could achieve what you need by creating a collection of roles and assigning different combinations of them to each user?
Try installing this Sitecore Module.This will clone the user in User Manager
SITECORE USER CLONE
Sitecore User Clone is used to create the copy of the user with the same roles, name, email, and profile. It will prompt to accept the new username, password and all the editable fields same like Edit user.