7 Learn: Frequently asked questions

• Can I update a user's Oracle Life Sciences single sign-on?
  Yes, an administrator can update the SSO of another user. In addition, users can manage their own Oracle Life Sciences single sign-on (SSO) accounts.
• Do I need to revoke access for SaaS Services users after collaboration is complete?
  No. SaaS Services users need to retain access rights for your instance of Oracle Clinical One Platform throughout its existence, so you should not revoke the access roles from these users. After a project ends, the accounts of the SaaS Services users expire within 60 days.
• Do I need to revoke access for Life Sciences Support users after a ticket is resolved?
  You can revoke access for Support if necessary. But, the Life Sciences Support team members working on the ticket can access your Oracle Clinical One Platform instance for two weeks (with the option to extend for one more week). After the two or three weeks, Support access expires automatically.
• How do I control users' access to the application?
  You assign users to roles at several levels.
• What happens if I change the roles assigned to a user while the user works in the product?
  The application updates every 15 minutes (approximately) while the user works in it.
• Does my organization need a user and site administrator?
  Every organization must have one or more user and site administrators and one or more global users.
• Can I create Oracle Life Sciences single sign-ons in Oracle InForm User Management Tool?
  If a site or sponsor user also works in Oracle InForm, you can create the Oracle Life Sciences single sign-on (SSO) for the user in Oracle Life Sciences IAMS or Oracle InForm User Management Tool.
• Who creates Oracle team members?
  Your Oracle project manager creates Oracle team members.
• How do I find my company's ShortOrgId?
  The <ShortOrgId> for your company appears in bold text in the New Account email you received from Oracle Identity Manager to activate your Oracle Life Sciences SSO.
• What should I do if I have a study that requires users to screen subjects and enter data before and after randomization, but not randomize them?
  This design solution gives you more control over when the Randomize button is available.