<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/273/all" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:og="http://ogp.me/ns#" xmlns:article="http://ogp.me/ns/article#" xmlns:book="http://ogp.me/ns/book#" xmlns:profile="http://ogp.me/ns/profile#" xmlns:video="http://ogp.me/ns/video#" xmlns:product="http://ogp.me/ns/product#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <channel>
    <title>Permissions</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/273/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/273/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Drupal permissions based on Workgroups</title>
    <link>https://swsblog.stanford.edu/blog/drupal-permissions-based-workgroups</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;What happens when the one guy who has access to manage users on your Drupal website leaves? Do you have a team of people that needs to work on the website, but those people change over time? Do they all have a SUNet ID? Take advantage of the Stanford WebAuth Module features and manage access by mapping Stanford workgroups to Drupal roles. &lt;/p&gt;
&lt;p&gt;&lt;a class=&quot;more-link&quot; href=&quot;http://workgroup.stanford.edu/&quot;&gt;Learn more about Stanford Workgroups&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 09 Mar 2015 18:00:00 +0000</pubDate>
 <dc:creator>Cynthia Mijares</dc:creator>
 <guid isPermaLink="false">505 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Getting Started on Sites: Remove Users Account Privileges</title>
    <link>https://swsblog.stanford.edu/blog/getting-started-sites-remove-users-account-privileges</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;Let&#039;s say your co-worker left Stanford or the grad student working on your website is no longer here. I&#039;ll walk you through the steps to either remove their editing privileges or cancel their account.&lt;/p&gt;
&lt;p&gt;After logging in the your website, navigate to the &lt;strong&gt;People&lt;/strong&gt; page.  In Stanford Sites Jumpstart products, go to the &lt;strong&gt;Site Actions&lt;/strong&gt; menu and choose &lt;strong&gt;Manage Users&lt;/strong&gt;.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 15 Sep 2014 15:47:06 +0000</pubDate>
 <dc:creator>Cynthia Mijares</dc:creator>
 <guid isPermaLink="false">415 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Using Display Suite to provide field-level permissions</title>
    <link>https://swsblog.stanford.edu/blog/using-display-suite-provide-field-level-permissions</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;Have you ever wanted to show only selected information on a content type to anonymous users and more information to authenticated users? It turns out that you can use Display Suite to provide field-level permissions for an entity.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 28 Jul 2014 15:00:00 +0000</pubDate>
 <dc:creator>Caryl J Westerberg</dc:creator>
 <guid isPermaLink="false">345 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>How to restrict content access</title>
    <link>https://swsblog.stanford.edu/blog/how-restrict-content-access</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;Need to restrict access to some content on your site? With the Content Access module, you can control viewing, editing, deleting permissions on your site by specific content types. Here&#039;s how to set it up.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Tue, 14 Jan 2014 16:06:36 +0000</pubDate>
 <dc:creator>Cynthia Mijares</dc:creator>
 <guid isPermaLink="false">259 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
