So, I've been working in SharePoint, and I want to restrict access to a column in a list in SharePoint, but I found that is not supported.
I have a type of incident management, where you create an incident, and it gets prioritized and moved around using workflows, and what I want to do is have an administrator of some sorts approve the incident, before it gets prioritzed and stuff. So my idea was simple, just have a field called 'approved' and a choice of true/false, and restrict the access of the field to an admin.
Are there any known workarounds for this, or do you have an idea I could try to get some what the same result?
Create an InfoPath form for your list, then have the "Approved" option only visible to your administrators. You could hard code the administrators into the form, or configure the form to use a SharePoint permission group.
Related
I have a custom people picker that fetches users from a SharePoint Group, only when the users are added manually from the Group settings.
If i add the users via SPD Workflow, the people picker is failing to read the data.
Deleted the Users and tried the Workflow, it didnt work. Removed app step from workflow and tried, still no use.
Reference to add User to SPD Group using Workflow: http://codelesssharepointinfopath.com/workflow-useful-rest-calls-add-user-to-group/
Expected: People Picker should show the users from the SPD Group
Actual: No Results found
It's probably because it's a workflow (if you're using 2010 give 2013 a try). Do you get the same issue when you use Flow? If you don't get the same issue I think you need to force a refresh via the workflow. Worst case scenario you can use REST to add the user to the group through the workflow and I would imagine that would force a refresh.
I am currently trying to set up a nintex workflow in SP 2010 that will run when an item is created in a list. Basically, users will be set in a custom permissions group before they create an item. When an item is created, the workflow will check for who created the item and then set that person in a different custom permissions group. From what I have found, the only way to do this is by using a call web service action, this requires credentials that I do not have access to. I was curious if there was a way to achieve the same permissions switch workflow without using the call web service action?
You could always use the action "change item permission" which should do the trick for modifying permissions to the item. you can assign it to either a person or group.
I would also suggest looking at a different route for managing item permissions. Change them at the item level is doable but can quickly become a nightmare if you want to revert things or figure out who has what after the 1000th item has been modified.
what the title says. I am not the farm administrator so I guess i don't have access to the sharepoint power shell. I am allowed to use sharepoint designer though and I guess I can set up a webpart that executes code even though I have never done it. I am open to any solution.
Thank you very much.
One way to get all the groups an user belongs to is by checking site permissions of that user
like explained in the article below,
http://office.microsoft.com/en-in/sharepoint-server-help/check-permissions-for-a-person-or-site-HA101794808.aspx#_Toc288817126
Once you enter the user name and check permissions, it will display all the group that user belongs to but you need to be part of the Owner group to enumerate other users' permissions this way.
I'm working on a branding site that allows anonymous users. By default it allows read access too all lists and libraries.
There are a few forms that gather information, and I want to allow anonymous users to add data, but they should not be able to view the list. I don't see any concept of 'deny' permissions.
This doesn't apply to all lists, just a few.
How is this done?
Thanks.
Edit
hmm, looks like on publishing sites that anonymous access to the forms sections is disabled by default.
http:///Lists//AllItems.aspx gives me a 401 unauthorized. That's good! Any danger here that I'm not aware of?
You can hide the list also, you can break inheritence on the list and assign custom permissions
I have a code activity that sends an email in a VS workflow. It simply sets the 'To' property to the name of a SharePoint group in the site collection. However, only the 1st person in the group gets emailed.
Any ideas why this is happening?
thanks
Does your group contain anything other than just users (ex: distribution lists, ad groups)?
If this is still a problem and you need to be able to send to a SharePoint group, I would recommend writing a custom workflow Action that would gather the emails of all the users in a specified group (you can find many tutorials online on how to make a custom action).
Turned out it was not even emailing the first user. I decided to extract the user emails programatically instead. Works fine.