Rangecast FAQ
[FAQ-1114] How Rangecast sets up permissions for an organization to grant access to user accounts



A Hub's basic parameters (number of authorized users, etc) can be established or modified by a Rangecast administrator, through a short form describing certain properties of the hub. Once established, the hub administrator may operate within the capacity limits and other guidelines defined in this form.


This action can only be taken by Rangecast administration.

1. Choose a hub name for the organization.

Note: For compatibility with current feed site software, the name should be limited to eight characters (with any mix of lower case alphabetic, numeric, and the dash; provided that at least the first character is alphabetic). This may be eased in the future.

2. Enter hub administration for that hub, using your Rangecast administration username/password

3. Choose the "Access License". Fill out this administrative section:

This describes the use of each field:

a) Open Access: Check this box if every Rangecast user should have permission to access content originating from this hub.

b) Fresh Account Access: Check this box if you want wildcard access (username *) in a License to include users who haven't been explicitly listed a license by any hub. (By default, users must be explicitly validated by at least one hub to have an active account. This checkbox bypasses that requirement.)

c) Usernames: This is a system capacity limit on the number of users who may use the Licenses issued by this hub. Note that this is zero for new hubs, and Rangecast administration must specifically set a capacity limit to unlock the hub's ability to grant access permissions to users.

d) Counter: For future use, leave blank unless a value is already present. This field relates to more precise control over capacity limits in systems with multi-user accounts (especially if embedding content in public websites.)

e) Go Back: This field sets a limit on how far in the past users may listen (if the user is using a License issued by this hub). The format is like "30m" for 30 minutes, or "4h" for 4 hours.

f) Delay: This field establishes a forced delay in releasing content, so users using licenses issued by this hub receive delayed content (instead of realtime content).

g) External Content: This field specifies any external content (not originating at an audio source with this hub in the feed site name) that the hub is allowed to grant permission to receive. Valid values include hubs and/or collections.

4. When complete, press "Save License" at the bottom of the page.

5. (Optional) Rangecast administration may give a Rangecast user at the organization owning the hub permission to administer the hub.

[FAQ-1115] How to grant or remove permission to administer a hub

In the hub administrative section for a hub, there is a list of Rangecast user accounts with administrative authority over the hub. This list may be edited to add or remove users from the hub's list of administrators. In addition to the accounts explicitly listed here, Rangecast administrators always have administrative authority over all hubs.


In order to grant users permission to access to particular channels, the hub administration must first have the authority from Rangecast to grant access to those channels.

A hub administrator automatically has permission to grant access to any channels brought into Rangecast by the hub's own feed sites (scanners or other audio sources). Since the hub owns these channels, their own administrators can always allow users to access this content.

By default, a hub administrator cannot grant access to any other content, since the other content is owned by other hubs. However, Rangecast can administratively permit exceptions to this default rule

[FAQ-1127] How a License written by one hub can grant authority to hear content received by another hub

By default, a hub administrator cannot grant access to any other content, since the other content is owned by other hubs. However, Rangecast can create exceptions to this general rule, so that content originating from one hub may be included in the Licence access grants written by another hub.




Rangecast FAQ - ID 1114 - last updated 18 October 2017     Images shown - [block]