1. © 2014 IBM Corporation External Collaboration IBM Connections 5.0 Workshop IBM Ecosystem Development Duration: 30 minutes

2. Agenda Introduction to External Collaboration Administering external users Granting roles to internal users

3. External Collaboration External User Collaboration provides a means for customers to bring external users into their Connections environment. External users will see only content shared with them and only the people associated with that content People can immediately identify external users External users have a targeted experience of the content and people in the organization who invited them Administrators can see who is an external user, can control who can invite them in, and can manage those accounts

4. Invite an external user to the Connections deployment If enabled, users can click here to open a company-specific page for registering new users The registration process is whatever process your company uses to bring users into your environment.

5. Create external community Community owners choose whether a community can allow external people Once this setting is made, it cannot be switched; you cannot change internal communities to external, or external communities to internal

6. Invite an external user to the new community External-facing communities are explicitly flagged Community owners can invite registered external users into the community

7. Share file with external user Files can be marked as able to be shared with external users Registered external users show up in typeahead

8. The external user logs in to Connections Icons and text take him to the correct place in the UI, and the bottom link goes to a help topic for external users.

9. The external user starts in the Home Page Greatly simplified home page and navigation. No personal microblogging, no viewing of any public data, no access to the company directory.

10. The external user enters the community External users have all rights of community members, but they cannot be community owners

11. External user can see business card, but not Profiles

12. External users never have access to public content or the company directory External users can search, but will not ever see public data returned External user can see any Files and Communities that he has been given access to.

13. Pictures and names of external users are flagged wherever they appear Internal user sees an indicator whenever he sees an external user's name or picture.

14. External-facing content is flagged whenever it appears Public Files User sees indicators on all external files and communities.

15. Users are warned before they comment User is warned before he comments on any files that can be seen by people outside of his company.

16. External users can do As an external user, you can perform the following tasks: Collaborate fully as members in communities, for example you can follow communities View and download files that are shared with you Edit files in IBM Docs View the activity stream to which you have access Edit your profile by clicking their picture and selecting My Profile View business cards of anyone that shares content with you Share files with people

17. External users cannot do As an external user, you cannot perform the following tasks: Be a community owner Create a community Follow people View public microblogs, public or moderated communities, public files View or search the company directory (including using type-ahead) to find people View recommended content or people Access the Profiles menu Access other user profiles View community metrics View Libraries shared within a partner Community (coming in 5.0 CR2/CCM Support)

18. Agenda Introduction to External Collaboration Administering external users Granting roles to internal users

19. Option 1: Set up Connections with 2 LDAP directories Setup a 2nd TDS directory for external users  Another branch in the same LDAP if required is possible Create a user login page with personalized text & terms Option 2: Work with IBM Services to create custom member management directory services TDI is used to synchronize external user data into Connections Roles for employee.extended (users who can create external facing community/file) must be set independently via wsadmin commands Registration Management

20. Registering external users with Profiles There are three ways to register a user. All methods set the value of mode to external to denote an external user. 1. Map a standard LDAP attribute for external users 2. Map a standard LDAP attribute using JavaScript 3. Use an LDAP branch to store external users For this lab we will use a LDAP branch to store external users. A secondary TDI directory has been created to make external users easier to manage. Use TDI.external directory to manage all external user population.

21. Use an LDAP branch to store external users 1) Edit map_dbrepos_from_source.properties Comment out the line: mode= Add or uncomment the line mode={func_mode_visitor_branch}. 2) In profiles_tdi.properties, specify the branch by updating the properties for source_ldap_url and source_ldap_search_base. source_ldap_url_visitor_confirm=ldap://localhost:389 source_ldap_search_base_visitor_confirm=ou=external,o=greenwell source_ldap_search_filter_visitor_confirm=(&(objectclass=inetOrgPerson)) 3) Append a string to an external user's display name in the map_dbrepos_from_source.properties displayName={func_decorate_displayName_if_visitor} displayNameLdapAttr=cn decorateVisitorDisplayName= - External User

22. External User Collaboration – Set up Enabling External User Collaboration on your platform: Edit the LotusConnections-config.xml true to true Disable anonymous access for your Connections instance. Set EMPLOYEE_EXTENDED role to the internal employees that can share content externally. wsadmin> ProfilesService.setRole(“lukas_geiger@greenwell.com”, EMPLOYEE_EXTENDED) Register external users into the Profiles DB using TDI.

23. Agenda Introduction to External Collaboration Administering external users Granting roles to internal users

24. EMPLOYEE_EXTENDED role By default, internal users cannot create content that is visible to external users. To allow collaboration between internal users and external users, you must assign the EMPLOYEE_EXTENDED role to the internal users. Only users with the EMPLOYEE_EXTENDED role can create content that can be shared with external users. However, the content can be shared by any internal user.

25. Setting user roles for external collaboration You may also set roles using a batch process. Documentation here.here

26. For Users with Rights to Create External Communities Simple checkbox to make Community externally visible. Only checkable if Restricted is selected. Once a Community is created as external, it's access level cannot be changed!