Setting up a Shared Domain

There are various ways to collaborate in the development of a website and to share your site content with others.

Content collaboration: To allow others to collaborate with you on your content there are several possible methods;

  • Share the URL to the content. There is an interface in the BYU Learning Suite that allows students to submit URL's for assignments. This can be useful when sharing a blog post or an online essay or even an online document (PDF)
  • There are document sharing tools that are allow for the sharing and even versioning of documents, presentations, media files and other content
  • There are applications that allow for the online collaboration and editing or commenting on documents and posts.
  • There are tools that are available for the sharing of posts or content to large or small groups

Website development collaboration

1. Each domain account is provided to a single Net ID. For personal domains, your Net ID and password should not be shared so that others can gain access to your domain to help you develop on it. You can provide them with alternate ways to access your personal domain account.

  • You can create FTP/SSH accounts that give them access to all or some of the directories in your domain.
  • You can create database access accounts to allow access to some or all of your databases
  • You can create user admin accounts to allow users access into each of your wp-admin accounts

2. We can create shared domain accounts that use a shared development team Net ID so a domain can be accessed by two or more developers.

Setting up a Shared Domain

Do you need a shared domain? Users that request or need this are usually trying to set up a BYU Domains account that needs to allow administrative access to the cPanel for multiple people (not just FTP accounts). Typical users that would benefit from this setup might be student employee web developers for a department, members of an official BYU club, professors, or teacher's assistants.

The reasoning behind this is that the individual owners of BYU Domains accounts, students in most cases, need to pay for their account if they want to keep their domain with BYU Domains after leaving the university. A shareable or group Net ID is meant for BYU affiliated clubs, employment groups, or departments that will need to grant access to users (students or developers) after the original users with access leave the university.

Want to learn more about how to set up a shared domain with BYU domains? See the video below.

Create Shared/Non-Person Net ID for Domain

To request a shared Net ID for a group domain, please email domains.support@byu.edu with the following information:

Preferred Net ID:

  • (to be created for the group, not a person in the group, see Note 1 )

Faculty Sponsor:(must be a full time employee/faculty member):

Preferred Domain Name:(make sure it is not already used by checking ICANN WHOIS )

Preferred Email Alias for the group:

  • Can be an existing @byu.edu address for the group, if not, an alias will be created under the faculty sponsor's account, see Note 2
  • This should not be the sponsors personal email!

Purpose of the shared account.

If the purpose is a class assignment/group project, give the user information about SSH and FTP accounts or documentation for their CMS about making admin accounts. If they have further questions, assign the ticket to the Domains Support Team.

Notes:
  1. The Preferred Net ID should not be an existing Net ID. The new non-person NetID should be associated with the group somehow. (Ex: Zumba Club: byuzumba)
  2. The email alias should be connected to the group (e.g. fhss@byu.edu, it@byu.edu). The Faculty Sponsor should provide consent for creation of the alias because it will be added to the Email Alias Manager of the Faculty Sponsor. The address should forward to the faculty sponsor's premium email.
  3. The Domain name needs to be available.

Users that are creating a website for a group project for a class (an assignment) or want to grant access to access to friends/developers etc should NOT be given a group Net ID. In these cases, direct the user to the wiki about information for FTP and SSH accounts or to their respective CMS documentation about administrative access for other users.