Difference between revisions of "Community Tenant"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 20: Line 20:


;Considerations:
;Considerations:
*Users added to the tenancies are automatically added as users in the Community to enable single sign-on access
:*Users added to the tenancies are automatically added as users in the Community to enable single sign-on access
:*The [[ISV]] can login to the community tenancy to see the list of site users
::*The [[ISV]] can login to the community tenancy to see the list of site users
:*The ''Community User'' associated with the Community Tenancy is based on the [[Username]]:
::*The ''Community User'' associated with the Community Tenancy is based on the [[Username]]:
::For Username of <tt>john@domainname.com</tt>, the ''Community User'' is  <tt>john@domainname.com.site</tt>
:::For Username of <tt>john@domainname.com</tt>, the ''Community User'' is  <tt>john@domainname.com.site</tt>
::''Learn more: [[Tenant System Administration|Tenant Ownership]]''
:::''Learn more: [[Tenant System Administration|Tenant Ownership]]''
*Users are automatically logged into the Community Tenancy application whenever they login to their tenancy
:*Users are automatically logged into the Community Tenancy application whenever they login to their tenancy
*Users are automatically logged out from the Community Tenancy application whenever they log out from the tenancy
:*Users are automatically logged out from the Community Tenancy application whenever they log out from the tenancy
*After the Community Tenancy is enabled, the User object in the community tenant should not have any required, user-defined field, otherwise addition of Users or Tenants will fail
:*After the Community Tenancy is enabled, the User object in the community tenant should not have any required, user-defined field, otherwise addition of Users or Tenants will fail
::*If ISVs is not planning to expose the Community Tenancy application registration to the public unless they also register for tenancy then the Community Tenancy username will never by needed by users and they need not know about this


:*If ISVs is not planning to expose the Community Tenancy application registration to the public unless they also register for tenancy then the Community Tenancy username will never by needed by users and they need not know about this
:*In addition to [[Sites#Tags|Site Tags]], ISVs can use services available in the [[Community Resource]] in the [[REST API]] to develop additional functionality
 
*In addition to [[Sites#Tags|Site Tags]], ISVs can use services available in the [[Community Resource]] in the [[REST API]] to develop additional functionality


===Enabling a Community Tenant with Existing Users===
===Enabling a Community Tenant with Existing Users===

Revision as of 01:38, 4 August 2011

The Community Tenancy feature can be used by ISVs to create community applications like Support Portal, Answers, Ideas and Social Networking.

The Community provides a space where all Users in all the tenancies (under a single ISV) can share knowledge and collaborate, without requiring a separate login to the platform.

Template:Tenantfeatures

How it Works

The ISV creates a new Tenancy, which serves as host to the Community. This Tenancy is managed via a login account, called the Community User.

All new Users in all the tenancies (under a single ISV) are then automatically associated with the Community account. This provides single sign-on capability via the community user credentials.

If the Community Tenancy feature is enabled in a tenancy with existing users, additional steps must be taken to make the association.

Learn more: Enabling a Community Tenant with Existing Users

Configure a Community Tenancy

  1. Complete the following steps to create a Community User (Linked Community Username):
    • Create a New Tenant
    • Create a Community Application in that Tenant via Sites
  2. In Service Provider Settings, enable Community Tenant Configuration from Service Provider Settings
Considerations
  • Users added to the tenancies are automatically added as users in the Community to enable single sign-on access
  • The ISV can login to the community tenancy to see the list of site users
  • The Community User associated with the Community Tenancy is based on the Username:
For Username of john@domainname.com, the Community User is john@domainname.com.site
Learn more: Tenant Ownership
  • Users are automatically logged into the Community Tenancy application whenever they login to their tenancy
  • Users are automatically logged out from the Community Tenancy application whenever they log out from the tenancy
  • After the Community Tenancy is enabled, the User object in the community tenant should not have any required, user-defined field, otherwise addition of Users or Tenants will fail
  • If ISVs is not planning to expose the Community Tenancy application registration to the public unless they also register for tenancy then the Community Tenancy username will never by needed by users and they need not know about this

Enabling a Community Tenant with Existing Users

To add existing Users in existing Tenancies to a Community Tenancy, complete the following steps:

  1. Create a Registration Page in the Community Tenancy
  2. Invite Existing Users to register using this page (send the link via Email)
  3. After Users register, use the LINK_TO_COMMUNITY_LOGIN service to link the Username with the Community User; Choose one of the following methods:
/networking/Service?s=243&a=link_to_community_login&community_login={COMMUNITY_LOGIN}&community_password={COMMUNITY_PASSWORD}
  • This Service can only be invoked by Tenant users after they have logged into their tenancy

After any one of the services has been executed successfully, the Username and Community User are now connected. From this point forward, when the user logs in to their tenancy, they are automatically logged in to the Community Tenancy.

Sync User Profile Information

By default, the User Profile in the Community Tenancy is automatically kept in sync with the user's Personal Setup Information, found in: My Information.

The following fields are automatically synchronized:

  • First Name
  • Last name
  • Email
  • Street
  • City
  • State
  • Zip
  • Country
  • Company
  • Title
  • Division
  • Phone
  • Fax
  • Mobile