Below are the six user types and the features they can use in MiLACNIC:
- Administrator:
This user manages resources and has no operational or viewing restrictions on the MiLACNIC platform. Within MiLACNIC, they can:
- Request, transfer, or return resources.
- Manage IPV4, IPV6, and ASN resources.
- Configure RPKI, IRR, Geofeeds, sub-assign blocks, and delegate rDNS.
- View and operate the Membership module: use or transfer training courses (Campus and webinars).
- Edit the organization's information and assign roles to other user types (change user IDs).
- View and operate the Payments module.
- Perform bulk operations.
- Access beta services.
- Make payments on behalf of other organizations.
2. Co-administrator:
This user has the same privileges as the Administrator, with the following exceptions:
- They cannot change IP block contacts, ASNs, or the organization itself.
- They cannot manage co-administrators.
- They cannot access beta Services.
Important: An organization has only one Administrator but can have multiple Co-administrators.
3. Membership Contact:
This user exercises their rights as a member. Within MiLACNIC, they can:
- View and operate the Membership module: use or transfer training courses (Campus and webinars).
- View and operate the Membership module: use or transfer training courses, with limited seats per member
- View and operate the Membership module: use or transfer tickets to annual events (two registration fee waivers).
- View and operate the Payments module.
- Make payments on behalf of other organizations.
4. Billing Contact:
This user is responsible for paying annual fees. Within MiLACNIC, they can:
- View and operate the Payments module.
- Make payments on behalf of other organizations.
- View and operate the Membership module: use or transfer training courses (Campus and webinars).
5. Technical Contact:
This user fulfills the technical role for the resources (IP addresses and/or ASNs) delegated by the Administrator. Within MiLACNIC, they can:
- Manage IPv4, IPv6, and ASN resources: sub-assign blocks and delegate rDNS.
- They cannot configure RPKI or IRR for the resources (this is limited to the Administrator and Co-Administrators).
- Define another person as the technical contact for the resource (the person who makes the change loses their technical contact status).
- View and operate the Membership module: use or transfer training courses (Campus and webinars).
- Add remarks for IP blocks.
6. Abuse Contact:
This user receives reports of security incidents involving resources (IP addresses and/or ASNs) delegated by the Administrator. Within MiLACNIC, they can:
- View and operate the Membership module: use or transfer training courses (Campus and webinars).
Comments
0 comments
Please sign in to leave a comment.