You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2021. It is now read-only.
It appears that SP REST Api support for adding and updating groups is relatively weak compared wtih other APIs. Is there anything that can be done witha d]
The text was updated successfully, but these errors were encountered:
Yes definitely.
Can we then set the group owner to a site wide standard "Site Owners" group
rather than the current user? And then the gross site access to read, or
perhaps the default is read?
Thanks
David
On Fri, 18 Jan 2019 at 3:58 pm, Brent Ely ***@***.***> wrote:
Something like these methods?
sprLib.site().groups().create('QA-Owners')sprLib.site().groups('Dev-Owners').addUser({ id:12345 })sprLib.site().groups('Dev-Owners').removeUser({ id:12345 })
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABlyL8ehtL28Z6RvG_FHkcTthRxzUj1Mks5vEVRngaJpZM4aFCcY>
.
--
All the best,
David Pratten
*Personal:* david@prattenmail.com
Mob: 0432 844 444
Postal: PO Box 1011, Sutherland NSW 1499, AUSTRALIA
*Work:* david.pratten@wesleymission.org.au
Senior Project Manager
Wesley Mission
Mob: 0429 420 885
Office: 220 Pitt St, Sydney 2000
It appears that SP REST Api support for adding and updating groups is relatively weak compared wtih other APIs. Is there anything that can be done witha d]
The text was updated successfully, but these errors were encountered: