Modifying your organization settings

You can modify your current organization settings as necessary. You must be an administrator to modify your organization settings. You can extend your organization's expiration date, change the user limit, and add additional storage space. Purchases can be made directly using the electronic forms provided or by contacting your ELB Learning sales representative.

For details about upgrading your trial account, see Upgrading your trial account.

To edit your organization settings:

1. Click the Org Settings link on the Getting Started page.

   The Org Settings window opens. See Viewing your organization settings for descriptions of the fields on this window.

2. Update the editable fields in the Org Settings window as follows. Some fields can only be updated by your organization's super-administrator.

   Organization Name	Name of the organization.
   Company Name	Name of the company.
   Disk Quota	Disk quotas track and control disk storage usage for each organization.
   Disk Usage Threshold	Disk usage thresholds allow you to specify when warnings are displayed to users when they exceed their disk quota limit.
   User Limit	Limits the number of users allowed in the organization.
   User Count	Displays the current number of users.
   Active	Disable this check box to deactivate the organization. Users are unable to log-in to a deactivated organization.
   Trial	Enable this check box to specify that this is a trial organization.
   Expires	Date when user access to the organization expires.
   Properties	Use this table to enable or specify the following publishing targets and organizational properties: Property Description Disable exporting projects When enabled, this restricts members of the organization from exporting projects with the exception of the organization administrators. This includes restricting exporting of library objects as well. Disable the creation of private projects When enabled, this restricts members of the organization from creating private projects, with the exception of the organization administrators. ELB Learning Agreement Select this option to allow users to access the ELB Learning Library. For more information, visit http://elblearning.com/. Publish to AICC The Aviation Industry CBT Committee (AICC) was established in 1988 to define standards on how Computer Managed Instruction (CMI) systems should operate in presenting course materials to students. For the latest specifications, documents, and explanations of terms, see the official AICC website (http://www.aicc.org). Publish to CourseMill CourseMill is a powerful course management system developed by ELB Learning and designed especially for easy integration of Lectora projects. The CourseMill learning management system makes the delivery, management, and tracking of online learning across your organization easier and more affordable. For more information about CourseMill, visit https://www.coursemill.com/. Publish to Docebo Select this option to allow users to post projects to the Docebo learning management system.. For more information about the Docebo LMS, visit http://docebo.com. Publish to Docebo: Server URL For Docebo publishing, specify the URL for accessing the appropriate server. Publish to Docebo: Username For Docebo publishing, specify the username for accessing the appropriate server. Publish to Docebo: Password For Docebo publishing, specify the password for accessing the appropriate server. Publish to HTML Select this option to allow users to post projects to the Internet or to their Intranet. Publish to iContent iContent is a content management system developed by SuccessFactors. For the latest specifications, documents, and explanations of terms, see their official website (http://www.successfactors.com/). Publish to iContent: course URL For iContent publishing, specify the URL for accessing the iContent course content on the iContent server. Publish to iContent: password For iContent publishing, specify the password for accessing the iContent server. Publish to iContent: path For iContent publishing, specify the path to the iContent server. Publish to iContent: server For iContent publishing, specify the address of the iContent server. Publish to iContent: username For iContent publishing, specify the username for accessing the iContent server. Publish to PWC PWC allows publishing content from the PricewaterhouseCoopers eLearning solution. For the latest specifications, documents, and explanations of terms, see their official website (http://www.pwc.com/). Publish to ReviewLink ReviewLink is an online review tool developed by ELB Learning. ReviewLink allows you to share projects with online reviewers and capture their feedback. Reviewers can add comments and attach files to reviewed pages to provide feedback. Comments and attachments are tabulated and presented to both publishers and reviewers so they can manage the status of the comments and complete the review cycle. For more information about ReviewLink, visit https://www.elblearning.com/create-learning/reviewlink. Publish to Saba SCORM 2004 Saba SCORM 2004 is a set of inter-related technical specifications built upon the work of the AICC, IMS, and IEEE to create a unified content model for Web-based learning content. For the latest specifications, documents, and explanations of terms, see the official Saba website (http://www.saba.com). Publish to SCORM The Shareable Content Object Reference Model (SCORM) is a set of inter-related technical specifications built upon the work of the AICC, IMS, and IEEE to create a unified content model for Web-based learning content. For the latest specifications, documents, and explanations of terms, see the official SCORM website (http://www.adlnet.gov/). Publish to SumTotal SumTotal allows publishing content from SumTotal eLearning systems. For the latest specifications, documents, and explanations of terms, see the official SumTotal website (http://www.sumtotalssystems.com/). Publish to xAPI The Experience API (xAPI) is part of an evolving standard that enables users on learning management systems to download the next generation of SCORM-compliant materials. For the latest specifications, documents, and explanations of terms, see the official xAPI website (http://experienceapi.com). Shared Project Maximum History Size Use the drop-down list to specify the setting for the maximum history size for shared projects. When versions are trimmed from a project's history they are taken from the "back-end" or oldest end. The version numbers will always rise as changes are checked in. So for example if you have a project with 10 versions (1 through 10) and you set the Maximum History Size to 3 then versions 1 through 7 will be removed from the project history (the oldest 7) leaving versions 8, 9 and 10. When the next check-in occurs, that will become version 11 and version 8 would be removed; leaving versions 9, 10 and 11. You keep the latest three versions basically. Note that the version trimming process does not take place immediately. Requests are queued up and run in the background. You should see results with in an hour generally. Also note that "status" versions (indicates that status of the project was changed) where the text is bold do not count towards the Maximum History Size. Consequently, you might have a Maximum History Size of 5 and the history shows 7 versions, but two of them are status versions. Shared Project Access - Team Only Select this option to restrict visibility of, and access to, shared projects to team members only. On the Manage Projects, Import/Export, and Project Search lists, only private projects and shared projects to which the user is assigned will be displayed. • This setting does not apply to administrators or project managers and can be overridden for individual Users. For additional information, see Adding a user and Viewing and editing user information.   • Some empty folders may not be visible. If a folder contains a project that is visible to you, then you will see the descendant folders of that folder (empty or not). Additionally, you will not see any empty folders (that do not contain projects) above that folder. Only the ancestor folders of that folder, if applicable, are visible. User Fonts Specify the custom fonts you want to be enabled within your organization. The fonts you specify will be displayed in the font lists for the users within the organization. The format to specify the fonts is specific: Start and end the entire entry with square brackets ([ and ]). Each font entry consists of the name of the font as you want it to appear in the font list and the font family name, separated by a comma. Separate multiple font entries with commas. Use single quotes around the first element in the font name if a space exists in the font name. Example: To enable new custom fonts Army and Navy and have them display as New Army Font and New Navy Font in the font lists, specify ["'New Army Font',Army","'New Navy Font',Navy"] For your users to develop projects that use a custom font, their projects must contain a HTML Extension object for the custom font. For details, see Enabling a custom font. You can also have users enable a custom font by creating and sharing a library object to insert into the project. For details about creating library objects, see Working with library objects.
   Administrator Notes	Administrator notes that were specified when the organization was created or modified.

3. Click Save.

The changes you make to your organization settings are implemented following purchase verification. Revisit the Org Settings window to verify that the correct changes were made.

Knowledge Base | Training | Support
© Copyright ELB Learning 2025