diff --git a/TL--documentation-new/.gitbook/assets/1 (15).png b/TL--documentation-new/.gitbook/assets/1 (15).png new file mode 100644 index 0000000000000000000000000000000000000000..c2250274990f737eb922c0cbe2c298865bb7f382 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (15).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b5aa78cf0d5538dbb3997ca434196e1172a4f210b1cf842a684b3f8548f25a4 +size 236006 diff --git a/TL--documentation-new/.gitbook/assets/1 (18).png b/TL--documentation-new/.gitbook/assets/1 (18).png new file mode 100644 index 0000000000000000000000000000000000000000..91614d5f716896cf414b10229d15f5471ab4028e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (18).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82d0fc6c2b9d994de2253b354a3bc29dc4b6e2dee74cb453a900ea4ac849a3be +size 124633 diff --git a/TL--documentation-new/.gitbook/assets/1 (19).png b/TL--documentation-new/.gitbook/assets/1 (19).png new file mode 100644 index 0000000000000000000000000000000000000000..854c873027dc874f9aa1bf0824407fd96e7cdb29 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (19).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba1b29c12325c9982463ebd23453b4d2e8ce50edbc74ef0e6f5f4b6cbba1b99d +size 209361 diff --git a/TL--documentation-new/.gitbook/assets/1 (41) (1) (2) (1).png b/TL--documentation-new/.gitbook/assets/1 (41) (1) (2) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..dba1c109bdde51c4b0953571f92ed790ed260b73 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (41) (1) (2) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3a7c40a1c20768cb045c0cc5e933a3d7733a4ee739bbdb32ee451ad98da7033 +size 37560 diff --git a/TL--documentation-new/.gitbook/assets/1 (42).png b/TL--documentation-new/.gitbook/assets/1 (42).png new file mode 100644 index 0000000000000000000000000000000000000000..01865acd173da33da6cf087325dcefd47944d0a7 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (42).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23d7cea9b88ded9674e89d6f355a4bc4520684f49c401fc4d3f151871c24f748 +size 80017 diff --git a/TL--documentation-new/.gitbook/assets/1 (45) (1).png b/TL--documentation-new/.gitbook/assets/1 (45) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..e6660eee8c90c12fc64419af3d6ddfc8062bf539 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (45) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5571e2284fbdeae0068a4f264e410cb8213b672e32472047ef891f717664ad6a +size 105588 diff --git a/TL--documentation-new/.gitbook/assets/1 (52) (1).png b/TL--documentation-new/.gitbook/assets/1 (52) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..a1738584ffc9874d38a37047616a22f8f1800769 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (52) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5213b5a54e16cc39013c41a4a9c6bbfeab8df2632a7afde911e4558c03968eb +size 102009 diff --git a/TL--documentation-new/.gitbook/assets/1 (53) (1).png b/TL--documentation-new/.gitbook/assets/1 (53) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..c0b2be4b3db96b997c5789d114b0851022a6be0d --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (53) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2baa4604a4fe4096724a54bb92274c88d7d5e5a49a863e149da423aa3e2f4c93 +size 100407 diff --git a/TL--documentation-new/.gitbook/assets/1 (54).png b/TL--documentation-new/.gitbook/assets/1 (54).png new file mode 100644 index 0000000000000000000000000000000000000000..31e5fcc6a831e75c82835b587f5a8fff25c7035f --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (54).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdd7551cf9a6d1600c80cb57dc3a058332cdbd93d717e995e68fcc479e73a0ed +size 66406 diff --git a/TL--documentation-new/.gitbook/assets/1 (58).png b/TL--documentation-new/.gitbook/assets/1 (58).png new file mode 100644 index 0000000000000000000000000000000000000000..f7ebab2567982f5949035fcd7cfec93c387067fa --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (58).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8539c31d0a0b336bd54af7a7cb5c5b2ded268032abb2d64e21070822d7044200 +size 72257 diff --git a/TL--documentation-new/.gitbook/assets/1 (59).png b/TL--documentation-new/.gitbook/assets/1 (59).png new file mode 100644 index 0000000000000000000000000000000000000000..f1c4c8029ce1bb0105cc9610549ef2c138da14a6 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (59).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09efe946f4a7cfc96ed30f626a91c296e454da8d1f4f022dbd6ba1c11f750d3c +size 186190 diff --git a/TL--documentation-new/.gitbook/assets/1 (6).png b/TL--documentation-new/.gitbook/assets/1 (6).png new file mode 100644 index 0000000000000000000000000000000000000000..a69b79ab01823eb79bf511867d467ceb09233eb0 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (6).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:300c0e8201b7db67c34b5c34b83637dab03c0452ec3469d260895e2281d0c34e +size 108333 diff --git a/TL--documentation-new/.gitbook/assets/1 (62) (2).png b/TL--documentation-new/.gitbook/assets/1 (62) (2).png new file mode 100644 index 0000000000000000000000000000000000000000..66128b1a62324c50ab386cddc87c463b262e3bcd --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (62) (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bee8fe91134aaca713ff789c24e60fa34ee5eab4ba25f62f0bc35dca91f9573 +size 43983 diff --git a/TL--documentation-new/.gitbook/assets/1 (62) (3).png b/TL--documentation-new/.gitbook/assets/1 (62) (3).png new file mode 100644 index 0000000000000000000000000000000000000000..ed08bbc19af8669b91080109e9474605c81fee27 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (62) (3).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b858f66de2e5149538b8e97dee8045c58077b8ccec86a8b0581d7e235e9bc8e +size 117869 diff --git a/TL--documentation-new/.gitbook/assets/1 (62).png b/TL--documentation-new/.gitbook/assets/1 (62).png new file mode 100644 index 0000000000000000000000000000000000000000..ed9facd426e054ffbaa54112f9e34e98f2cb4c37 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (62).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc55a96d7c79120dc7af45238c437e690074ff73cb8b2ad6f20e211518c5c2cd +size 117327 diff --git a/TL--documentation-new/.gitbook/assets/1 (63) (2).png b/TL--documentation-new/.gitbook/assets/1 (63) (2).png new file mode 100644 index 0000000000000000000000000000000000000000..3d43031efae27428ce55f005f99f0543eb886b0b --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (63) (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3405734e94e7e55950f2810e9e8ef4d11f21d265284b7656c7198ee888c6988f +size 145796 diff --git a/TL--documentation-new/.gitbook/assets/1 (63) (3).png b/TL--documentation-new/.gitbook/assets/1 (63) (3).png new file mode 100644 index 0000000000000000000000000000000000000000..5acfe218d0bd13d8da3cd933c777d5127d5738d7 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (63) (3).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:520266ec2114265396a400e99c11f1b427be0fb97849655c62ba555911e06a30 +size 214408 diff --git a/TL--documentation-new/.gitbook/assets/1 (63).png b/TL--documentation-new/.gitbook/assets/1 (63).png new file mode 100644 index 0000000000000000000000000000000000000000..1cce4ad23a3d8c9bab582293afdf86c8c71d5273 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (63).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e69bb6c73f7ac0c1d5599683b0da714ea26200c41756778469ab9180abd93068 +size 105595 diff --git a/TL--documentation-new/.gitbook/assets/1 (64) (5).png b/TL--documentation-new/.gitbook/assets/1 (64) (5).png new file mode 100644 index 0000000000000000000000000000000000000000..5dd78012811dfab0a1b597021f18a19f74901f13 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (64) (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d24489dc2333598f7f44a39d98b5c63506d2e28aced0bae22c1d23e378ea473 +size 191171 diff --git a/TL--documentation-new/.gitbook/assets/1 (65) (5).png b/TL--documentation-new/.gitbook/assets/1 (65) (5).png new file mode 100644 index 0000000000000000000000000000000000000000..15c1496a3e82eda08cd766e48b79995a7387bfe3 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (65) (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10c59baaaacebde5e764fb94ac4e0e74bff5bfb94b8281341e9fcb73786fd83f +size 113561 diff --git a/TL--documentation-new/.gitbook/assets/1 (68) (2).png b/TL--documentation-new/.gitbook/assets/1 (68) (2).png new file mode 100644 index 0000000000000000000000000000000000000000..71c5c3459cc5dfdccf355f2e4d897833b538f228 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (68) (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cab44769f827d28630f8a181982c925816722977a2ffd7801eff61ffb7cc6412 +size 112558 diff --git a/TL--documentation-new/.gitbook/assets/1 (7).png b/TL--documentation-new/.gitbook/assets/1 (7).png new file mode 100644 index 0000000000000000000000000000000000000000..7716b0783cfe175133098bf4fe92a1d94cc69ada --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (7).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:709eff1cfa146ce34b4b3c95deb144fda05117c2a0ed9e144aed7b0a740f375d +size 119014 diff --git a/TL--documentation-new/.gitbook/assets/1 (70) (1).png b/TL--documentation-new/.gitbook/assets/1 (70) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..b7e6171f86548576f75c21c1dde05d34bf0b2334 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (70) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bdb3383f9e7e8f64ca6f263da644c9b15afd41f8135ceaf86b65b866d99b855 +size 145398 diff --git a/TL--documentation-new/.gitbook/assets/1 (71) (1).png b/TL--documentation-new/.gitbook/assets/1 (71) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..407581630408d72f9b9d26c6b0bc7ced58fa0dce --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (71) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b5e86fa4a7a40b24d8627858729326d27ef327ed4ab6ed1196bc973e35badac +size 143281 diff --git a/TL--documentation-new/.gitbook/assets/1 (72) (4).png b/TL--documentation-new/.gitbook/assets/1 (72) (4).png new file mode 100644 index 0000000000000000000000000000000000000000..0efae20ab0dbdd54359417a8f20a17a0cb67889a --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (72) (4).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:942f302e31eea2884dd979c65cf1b41aafdb133cd651f890f406ae3c4b3fe2c5 +size 147340 diff --git a/TL--documentation-new/.gitbook/assets/1 (73) (4).png b/TL--documentation-new/.gitbook/assets/1 (73) (4).png new file mode 100644 index 0000000000000000000000000000000000000000..6a336710c55ac78db78825c36be8bb87c727c2b0 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (73) (4).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d09a095903a70ca3317f0f5a6a944433ea9ccf7ad64ff493bc5be0f309c8f3c +size 166522 diff --git a/TL--documentation-new/.gitbook/assets/1 (74).png b/TL--documentation-new/.gitbook/assets/1 (74).png new file mode 100644 index 0000000000000000000000000000000000000000..e5a4b3cb945721ecda0029d9ea39aa26a5d4c18e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (74).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6268662a5cfaa412f259331754d103958ef11cfb0eff69168fd4bad6bcf98474 +size 120649 diff --git a/TL--documentation-new/.gitbook/assets/1 (75).png b/TL--documentation-new/.gitbook/assets/1 (75).png new file mode 100644 index 0000000000000000000000000000000000000000..8ed4fb60455e663378d11caebbf81d1c8e55c6a2 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (75).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adafff133d106f8cd596f17c82a666cc5f44e201daf2e648e97f1aeae7f0d109 +size 39639 diff --git a/TL--documentation-new/.gitbook/assets/1 (94) (1).png b/TL--documentation-new/.gitbook/assets/1 (94) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..18e2636477636732e36d424d238aaf3d810e4b86 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/1 (94) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e20d6b6f2b311b8676718ab4313b11e7e4f7e505ff9736d0802bb9c3e46af0e8 +size 86051 diff --git a/TL--documentation-new/.gitbook/assets/10 (1).png b/TL--documentation-new/.gitbook/assets/10 (1).png new file mode 100644 index 0000000000000000000000000000000000000000..0038d95e2df15bed92fb07e1a830b1f04e066dc3 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/10 (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a05cfc22e2eb3c697f799fe2a37fc56e84acc461d3dd5f59096b9faa436cb30 +size 198950 diff --git a/TL--documentation-new/.gitbook/assets/11 (1).png b/TL--documentation-new/.gitbook/assets/11 (1).png new file mode 100644 index 0000000000000000000000000000000000000000..6dc941e41e17a43c2272040d9a05bbfdbd1d0907 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/11 (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65530f45287fa0f53687034347df59053494045a6c6f3e615a89524974208746 +size 198133 diff --git a/TL--documentation-new/.gitbook/assets/2 (1).jpg b/TL--documentation-new/.gitbook/assets/2 (1).jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bbeb67186c021123668046b6bfb51d33906305e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/2 (1).jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d6cd37f1b9b2bcb8647478bef78c2666da06614fe4fc5a137573b49100aa7a9 +size 204881 diff --git a/TL--documentation-new/.gitbook/assets/2 (1).png b/TL--documentation-new/.gitbook/assets/2 (1).png new file mode 100644 index 0000000000000000000000000000000000000000..154194ad16aee02e55b88ff88af32b191de6eb02 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/2 (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0d864e1a571eac6759be3a298274daef78d303f96317b30a2aacc2119f38cbb +size 255345 diff --git a/TL--documentation-new/.gitbook/assets/2 (10).png b/TL--documentation-new/.gitbook/assets/2 (10).png new file mode 100644 index 0000000000000000000000000000000000000000..d4ecf4ea39f321d862eb004964fbd977c2a78613 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/2 (10).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3df7f377f9049629f090756983680404f1726acacbf9d65b13110c2fc9826514 +size 60052 diff --git a/TL--documentation-new/.gitbook/assets/2 (11).png b/TL--documentation-new/.gitbook/assets/2 (11).png new file mode 100644 index 0000000000000000000000000000000000000000..60673ecca783e1770e46200a8820cda6c81a508d --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/2 (11).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80109ebc1efbf3df3298099b5de00c42ee7c85fe63981194cffe55b2545d0693 +size 70997 diff --git "a/TL--documentation-new/.gitbook/assets/2022-12-09 13_23_52-Activity \342\200\223 prcord.xyz \342\200\223 Stripe.png" "b/TL--documentation-new/.gitbook/assets/2022-12-09 13_23_52-Activity \342\200\223 prcord.xyz \342\200\223 Stripe.png" new file mode 100644 index 0000000000000000000000000000000000000000..f880a554547df1a4b5d2fc0d6c644fb01bb07a69 --- /dev/null +++ "b/TL--documentation-new/.gitbook/assets/2022-12-09 13_23_52-Activity \342\200\223 prcord.xyz \342\200\223 Stripe.png" @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dc23124937d737f422b3860b2f9b9732a6d0680e44248ec71ea5bd958af63e1 +size 38546 diff --git a/TL--documentation-new/.gitbook/assets/3 (1).jpg b/TL--documentation-new/.gitbook/assets/3 (1).jpg new file mode 100644 index 0000000000000000000000000000000000000000..8948e72dd40d7fdf597a22ed377bf76882c92fdd --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/3 (1).jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11fe7ffb8ea4b5ace79e30b5a3473b58badbfd7c71bdb3eb445a3af3cb30ebd4 +size 95992 diff --git a/TL--documentation-new/.gitbook/assets/3 (1).png b/TL--documentation-new/.gitbook/assets/3 (1).png new file mode 100644 index 0000000000000000000000000000000000000000..2b49c657ebda236dc2402e18a9559718eed757e3 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/3 (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:993c2ac232b79fa0c08646f350fe551a1420b121bdce3e56738b5d6988edc3ee +size 35467 diff --git a/TL--documentation-new/.gitbook/assets/3 (10).png b/TL--documentation-new/.gitbook/assets/3 (10).png new file mode 100644 index 0000000000000000000000000000000000000000..171c291efd335e805eb7ca3888d00cede82f2986 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/3 (10).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b4b9f0871cf650b48b8fad07cc79d9eb8f44a36816e5ac87fc6a954231b80d1 +size 15901 diff --git a/TL--documentation-new/.gitbook/assets/3 (11).png b/TL--documentation-new/.gitbook/assets/3 (11).png new file mode 100644 index 0000000000000000000000000000000000000000..16bb85d534c8512d759682104b0ff13a2bb54504 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/3 (11).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15d5ed15f822aa62d833b8ed70e5f03580d55e47e2012ef791c0aff5a3d8d9c9 +size 106114 diff --git a/TL--documentation-new/.gitbook/assets/4 (5).png b/TL--documentation-new/.gitbook/assets/4 (5).png new file mode 100644 index 0000000000000000000000000000000000000000..3998a45062f3852fa2ecf2f6d4ebf8b447965610 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/4 (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b54d05bb73d16ca86f073c95175c41b3ca99f71015a9f0c5f2092007dce94e6b +size 108506 diff --git a/TL--documentation-new/.gitbook/assets/4 (9).png b/TL--documentation-new/.gitbook/assets/4 (9).png new file mode 100644 index 0000000000000000000000000000000000000000..1978b4b546fc1b3eb1d072e441aafcf7b34e54b7 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/4 (9).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75554c1bf20f597864207cd852fa2b5fad09af4ca17191a8606785effbadb668 +size 56280 diff --git a/TL--documentation-new/.gitbook/assets/5 (4).png b/TL--documentation-new/.gitbook/assets/5 (4).png new file mode 100644 index 0000000000000000000000000000000000000000..3a993480156129ef9f4520746e941674117258d2 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/5 (4).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92d3e53ee22951881e294c38ff792013a7bb3322e448d7df030c8a5810b5d415 +size 103367 diff --git a/TL--documentation-new/.gitbook/assets/5 (5).png b/TL--documentation-new/.gitbook/assets/5 (5).png new file mode 100644 index 0000000000000000000000000000000000000000..3a993480156129ef9f4520746e941674117258d2 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/5 (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92d3e53ee22951881e294c38ff792013a7bb3322e448d7df030c8a5810b5d415 +size 103367 diff --git a/TL--documentation-new/.gitbook/assets/5 (8).png b/TL--documentation-new/.gitbook/assets/5 (8).png new file mode 100644 index 0000000000000000000000000000000000000000..e8841e21aa71d9ad4f2fc8097ec2ec9c4964450e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/5 (8).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b20da23c4d9626caf3f01a7f72d1fca31816e393695e74d02024a53fd3a7437f +size 4330 diff --git a/TL--documentation-new/.gitbook/assets/5.1.jpg b/TL--documentation-new/.gitbook/assets/5.1.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1be3b0cfff885af67e1ae01658154dd47759e7e6 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/5.1.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb7b9595cd45cfe6ab0679d6072e75b5f7168fde7bc93612fe57e7b58664f881 +size 102358 diff --git a/TL--documentation-new/.gitbook/assets/5.2.jpg b/TL--documentation-new/.gitbook/assets/5.2.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49ff408ec2777703b19eb0be9b26955b053bea19 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/5.2.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70127392040df77a10c7a1d35efcefb2aefcebfb6d7a87f9832ff21501d3f9c1 +size 197924 diff --git a/TL--documentation-new/.gitbook/assets/6 (2).png b/TL--documentation-new/.gitbook/assets/6 (2).png new file mode 100644 index 0000000000000000000000000000000000000000..f1924c3fc93afffe2a62cd6cb9403add9004493b --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/6 (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:388940b22e6048f4d68ed7aead3d0a0f242efc4e6a9f931d75a7f691eb1fcf91 +size 167530 diff --git a/TL--documentation-new/.gitbook/assets/6 (3).png b/TL--documentation-new/.gitbook/assets/6 (3).png new file mode 100644 index 0000000000000000000000000000000000000000..b8c4d9c92da30a95024a32ac3be2c4ae8f63adfc --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/6 (3).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f797844eb81811980557c4f25e1a7d3e36deaddcfd488688d1b6759a0a6dbfe9 +size 87935 diff --git a/TL--documentation-new/.gitbook/assets/7 (2).png b/TL--documentation-new/.gitbook/assets/7 (2).png new file mode 100644 index 0000000000000000000000000000000000000000..94a99530b7019868eed16623f6c37832eee8f8a1 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/7 (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:772529d2cfb1c39f7ab721f0e0e2d0a6e14687740e1d417ae409cb19e7ba4ac3 +size 87868 diff --git a/TL--documentation-new/.gitbook/assets/7 (3).png b/TL--documentation-new/.gitbook/assets/7 (3).png new file mode 100644 index 0000000000000000000000000000000000000000..c94bc0ce4e975cc39486c20cd987cc23724c7196 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/7 (3).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c76670ecced95911a94621733348800c4cd8fc415765f34fd0b6806498d44b7 +size 54113 diff --git a/TL--documentation-new/.gitbook/assets/Group_171 (1).jpg b/TL--documentation-new/.gitbook/assets/Group_171 (1).jpg new file mode 100644 index 0000000000000000000000000000000000000000..183ba3449b050d116dfc0857ad330376d3f08a96 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Group_171 (1).jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c223f69168aaf853780bb9f0a0cc7ec6ab0ae95c63ba816e3e3f7e16d1bcbfb +size 140603 diff --git a/TL--documentation-new/.gitbook/assets/Group_171.jpg b/TL--documentation-new/.gitbook/assets/Group_171.jpg new file mode 100644 index 0000000000000000000000000000000000000000..183ba3449b050d116dfc0857ad330376d3f08a96 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Group_171.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c223f69168aaf853780bb9f0a0cc7ec6ab0ae95c63ba816e3e3f7e16d1bcbfb +size 140603 diff --git a/TL--documentation-new/.gitbook/assets/IP Royal.png b/TL--documentation-new/.gitbook/assets/IP Royal.png new file mode 100644 index 0000000000000000000000000000000000000000..403cc0ec4df22c1ebaa04bf9092793fa8aa6588e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/IP Royal.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc5667b2ee3ce7364e55030a181a9a804bb1fe7e854854c99a6d9c68d977e1ff +size 95866 diff --git a/TL--documentation-new/.gitbook/assets/Screen Shot 2022-01-23 at 7.56.05 PM.png b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-01-23 at 7.56.05 PM.png new file mode 100644 index 0000000000000000000000000000000000000000..0176e1902e7ece5d5ab6335d9c883a1e57b18406 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-01-23 at 7.56.05 PM.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d3022affdbf896b632d222bb1a2c650b8c5171e486ff2f3c7c444514f40d76f +size 126531 diff --git a/TL--documentation-new/.gitbook/assets/Screen Shot 2022-01-23 at 8.10.17 PM.png b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-01-23 at 8.10.17 PM.png new file mode 100644 index 0000000000000000000000000000000000000000..14da0c71c2aef884957e141eb8b4432ac8630dfc --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-01-23 at 8.10.17 PM.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46b43195de31ad0b1b354033de7b8d7805d2af765830ab55ee24cdeb9df85b8a +size 113159 diff --git a/TL--documentation-new/.gitbook/assets/Screen Shot 2022-03-20 at 3.45.33 PM (1).png b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-03-20 at 3.45.33 PM (1).png new file mode 100644 index 0000000000000000000000000000000000000000..5b87b62d6c236544352145cf68f4cfbab4bb3c21 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-03-20 at 3.45.33 PM (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be4a2a5bbfa6fc7333d13915d3ae235fe76dd89396fa9ace87783f5bd684a4fb +size 61943 diff --git a/TL--documentation-new/.gitbook/assets/Screen Shot 2022-03-25 at 7.52.39 PM.png b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-03-25 at 7.52.39 PM.png new file mode 100644 index 0000000000000000000000000000000000000000..25ee4eb71ff9279956c6a2cdd6188b7187a9624f --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-03-25 at 7.52.39 PM.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5963889efaec558665b0e7f717b02b124143fb78175be2c0a805b5519c8afdc4 +size 64666 diff --git a/TL--documentation-new/.gitbook/assets/Screen Shot 2022-06-26 at 12.41.56 PM.png b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-06-26 at 12.41.56 PM.png new file mode 100644 index 0000000000000000000000000000000000000000..c2a8feb87e6bb26c0a8fcc13408d68aaf6bf8f47 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-06-26 at 12.41.56 PM.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a4fa08be3ae44509785fafe424d63396b23904159f3d0a5d6c021042e8ffe98 +size 209079 diff --git a/TL--documentation-new/.gitbook/assets/Screen Shot 2022-08-31 at 10.14.31 AM.png b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-08-31 at 10.14.31 AM.png new file mode 100644 index 0000000000000000000000000000000000000000..42d29614eaa073a86e49e8f8a0bcdbb8bc8e0ebe --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-08-31 at 10.14.31 AM.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:332ab8fa8d0280092fff928f58da54921462d79bfb42d7f7049570435e4a3cf8 +size 108299 diff --git a/TL--documentation-new/.gitbook/assets/Screen Shot 2022-08-31 at 10.14.37 AM (1).png b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-08-31 at 10.14.37 AM (1).png new file mode 100644 index 0000000000000000000000000000000000000000..fa7ea1647558ef6cd6808ca627eaad1566e9b525 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen Shot 2022-08-31 at 10.14.37 AM (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cd543e99a32b014271101909d3b30124f1c27f1321ceb63142721ed869638cb +size 61657 diff --git a/TL--documentation-new/.gitbook/assets/Screen_Shot_2022-06-22_at_4.19.36_PM (1).png b/TL--documentation-new/.gitbook/assets/Screen_Shot_2022-06-22_at_4.19.36_PM (1).png new file mode 100644 index 0000000000000000000000000000000000000000..0c78c0de8208c160cd3d54d5bb5d814d686849bf --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screen_Shot_2022-06-22_at_4.19.36_PM (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc9ea575ebe95639b2a827483fd939d183ebec3be2c51015a1163d77c4518f2a +size 76743 diff --git a/TL--documentation-new/.gitbook/assets/Screenshot (149).png b/TL--documentation-new/.gitbook/assets/Screenshot (149).png new file mode 100644 index 0000000000000000000000000000000000000000..dc070eefd42d3438bb0b12fec8e38fec88a2942d --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screenshot (149).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ef1ebe044281a05a514bc4746715eead10bd10e3fecf408f59deb969cef18a5 +size 159340 diff --git a/TL--documentation-new/.gitbook/assets/Screenshot (87) (1).png b/TL--documentation-new/.gitbook/assets/Screenshot (87) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..012e512ddb985078b5977ff17dea6a35e962eb96 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screenshot (87) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddb534e38c9f4dfad7305d908e19bbdae5133a391fea9c566ebe25a1cdaea4fb +size 122056 diff --git a/TL--documentation-new/.gitbook/assets/Screenshot (966) (1).png b/TL--documentation-new/.gitbook/assets/Screenshot (966) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..d42b750a4bec64f0ced922c188e6df6e2ced7656 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screenshot (966) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18e35543e40c043e9711421c6598ca9d2039a9e4012c214cc4608b0fb2686af4 +size 14197 diff --git a/TL--documentation-new/.gitbook/assets/Screenshot 2023-03-20 at 11.23.24.png b/TL--documentation-new/.gitbook/assets/Screenshot 2023-03-20 at 11.23.24.png new file mode 100644 index 0000000000000000000000000000000000000000..be855dd17ab61bbd4e76ab0316dd2c29c2faef39 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Screenshot 2023-03-20 at 11.23.24.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cb7b682c33ad6804cd526d3c0f866ba8da074a6e8c8ce60bdad7dc594a580fe +size 84017 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (1) (4).png b/TL--documentation-new/.gitbook/assets/Untitled design (1) (4).png new file mode 100644 index 0000000000000000000000000000000000000000..ae9484dc8c6aa99e95e767cf1d986a73576c6541 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (1) (4).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcc683f4bb02b10e34f91bb283ff931dc4ae704e980f9b1279a2397ba87f49e1 +size 80803 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (1) (5).png b/TL--documentation-new/.gitbook/assets/Untitled design (1) (5).png new file mode 100644 index 0000000000000000000000000000000000000000..7425548c01e3ef58a71975855163c8a05b6b3137 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (1) (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e46bcf823aa6ec70fbf9db560fbc5a2447889e7de76f2a269f41239013d0a93e +size 131062 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (1) (8).png b/TL--documentation-new/.gitbook/assets/Untitled design (1) (8).png new file mode 100644 index 0000000000000000000000000000000000000000..c3e6dc15d576cee609e9243e508bc67dd060587b --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (1) (8).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aff88b9c8f3f196d71d210e3c3cef580ec678bf48184dfdf7d5441fa9fb1ed4 +size 112541 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (10) (5).png b/TL--documentation-new/.gitbook/assets/Untitled design (10) (5).png new file mode 100644 index 0000000000000000000000000000000000000000..1ec66a779de1180f400aff60a87f450c881155b1 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (10) (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09f5b2ac7e44e515880e4326c6b62cea2e9cd3317363fa20240c85bb88409f26 +size 202338 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (11) (5).png b/TL--documentation-new/.gitbook/assets/Untitled design (11) (5).png new file mode 100644 index 0000000000000000000000000000000000000000..5dd845d15b842af4dae292deff8c26eac2c10c88 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (11) (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:435b4f40a06c5af3da8d2620b299808bb34432014ce17d481ba57f010e7397f9 +size 137040 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (12) (1).png b/TL--documentation-new/.gitbook/assets/Untitled design (12) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..ac83e18b662fc865da4bac9c7330327c5da8ea87 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (12) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c076408fd72972337f36bf3e38d37195cb6e3e54cd4c7317f72553fb4a52224d +size 104776 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (13) (1).png b/TL--documentation-new/.gitbook/assets/Untitled design (13) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..8b986994a11bb860d0be0bc86d9cc3f2535abcf7 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (13) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d81db2c4a51a36a0eaf8a9d3d6024c2752b051e9a641f524ed15c0ba75774fa +size 104847 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (17).png b/TL--documentation-new/.gitbook/assets/Untitled design (17).png new file mode 100644 index 0000000000000000000000000000000000000000..baccc254f4fd7519a18404a5cb5d6d7e0154caa7 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (17).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d9bce76d3de31d707652e142cd075fa766a8bde575b0c982bbf14b6fecd52df +size 178889 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (2) (1).png b/TL--documentation-new/.gitbook/assets/Untitled design (2) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..cc33991c178dc08b18e92da26d06d301de51ec25 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (2) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ee02a3348b674e9a9c976bf7c937b9afea17201075340dccaf40a0477c9a58b +size 51294 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (2).png b/TL--documentation-new/.gitbook/assets/Untitled design (2).png new file mode 100644 index 0000000000000000000000000000000000000000..9466c425663b2b47f3d6b2d0531385fb3efe9b7e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a2790f7875803e6e7e62902f5e1d452c93fd731364354c982df5d8167b5d9d9 +size 143864 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (20).png b/TL--documentation-new/.gitbook/assets/Untitled design (20).png new file mode 100644 index 0000000000000000000000000000000000000000..ef41c54078f7ee7891864e93ec5ae58ee7976fc1 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (20).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6965f24fbba1580d084d2e130eda16d5832a9f5f5e930621baccd39a606ad96 +size 86209 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (21).png b/TL--documentation-new/.gitbook/assets/Untitled design (21).png new file mode 100644 index 0000000000000000000000000000000000000000..3c685ae0d7122dd1107d4b1fe203df621ef2c055 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (21).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf94c12e5ef50c32ea35429915ed4692e0141ec4bf3b05717faf820c6d0f6047 +size 76960 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (22) (2).png b/TL--documentation-new/.gitbook/assets/Untitled design (22) (2).png new file mode 100644 index 0000000000000000000000000000000000000000..dda5bbd91e3878cf3b8270af5e5e050b249fe7ae --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (22) (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dab9277ee989c13f41bc9980f20bbc9bf4f63c1e20fff2823692399a5e16fed +size 134422 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (3) (1).png b/TL--documentation-new/.gitbook/assets/Untitled design (3) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..1e6063ac35be1c2c8362eb2d0ba04aef4f6df8b7 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (3) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13501574533b1931f970980d16cce9989a7287c4e344be217abe4b9127c220fa +size 76970 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (3) (10).png b/TL--documentation-new/.gitbook/assets/Untitled design (3) (10).png new file mode 100644 index 0000000000000000000000000000000000000000..e57efc503aa9b47b3ae55b23a23eb0770401d188 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (3) (10).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:358969d7c16bfcd58fe581f8b3e801c9c2c1a817029994734135a49025fef48c +size 87666 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (3).png b/TL--documentation-new/.gitbook/assets/Untitled design (3).png new file mode 100644 index 0000000000000000000000000000000000000000..4424d725c24ed0dc70f04cd58e4e060bdcf4fdeb --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (3).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32e108a55b990262879e0cfe80fdb17be1117f9773352eec984319e592626dde +size 183250 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (4) (6).png b/TL--documentation-new/.gitbook/assets/Untitled design (4) (6).png new file mode 100644 index 0000000000000000000000000000000000000000..e539432badcbbcef70c052434863501ff0a1b859 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (4) (6).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd9e8dda26c5d9af8658f6281702656798c2211fbabaa84c1867d05678646ee9 +size 278257 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (5) (6).png b/TL--documentation-new/.gitbook/assets/Untitled design (5) (6).png new file mode 100644 index 0000000000000000000000000000000000000000..c14fd71121bfa9c18899458747f204f34a94181c --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (5) (6).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8206eb980cff1ace998273e2a07ed06d0843f482ca8a3472946f90ba458d112d +size 90488 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (6) (2).png b/TL--documentation-new/.gitbook/assets/Untitled design (6) (2).png new file mode 100644 index 0000000000000000000000000000000000000000..9d263d2460d66172d4b5ef79431f10e3f699707e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (6) (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc1c998777cf4363adb4d1c165e27eee77db9bfce7ea81ee19233da4eee4b33b +size 90435 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (6) (3).png b/TL--documentation-new/.gitbook/assets/Untitled design (6) (3).png new file mode 100644 index 0000000000000000000000000000000000000000..88f8315d5e14b41ac5cda281dd85fee6571561b0 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (6) (3).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dceb97be33f717ce9f148adb2079ec78b77ee4bc445db57df616fd015336405c +size 189238 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (7) (2).png b/TL--documentation-new/.gitbook/assets/Untitled design (7) (2).png new file mode 100644 index 0000000000000000000000000000000000000000..b9a37608f7488cfde36692919ca2b4f48c38b96a --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (7) (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afddbb9526a30f693c8afb8f219f65606c4c77b270cb39d35afbd0538305a78b +size 90337 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (7) (3).png b/TL--documentation-new/.gitbook/assets/Untitled design (7) (3).png new file mode 100644 index 0000000000000000000000000000000000000000..c2275f5751db042c3ecbec77699d294c3620f926 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (7) (3).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10dd96654e7a6d4fe2bb2e37c5aa8936049845ec6f6bbee27dea429c00040bbb +size 83236 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (8) (1).png b/TL--documentation-new/.gitbook/assets/Untitled design (8) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..af9a9ac7f38506492478f6fad336ce4177925e6f --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (8) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:261b89cb9da18c7688551684d4da62e0b681888d02b508951ab369f1b45d1cca +size 99336 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (8) (10).png b/TL--documentation-new/.gitbook/assets/Untitled design (8) (10).png new file mode 100644 index 0000000000000000000000000000000000000000..c04c531708ece275c097bfb87bae9f6af963bfcb --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (8) (10).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4e31233a9cd3703edaa6905cf613f56e8e6e13e5b15f2d4d4a981c967f67a9d +size 88041 diff --git a/TL--documentation-new/.gitbook/assets/Untitled design (9) (1).png b/TL--documentation-new/.gitbook/assets/Untitled design (9) (1).png new file mode 100644 index 0000000000000000000000000000000000000000..4b347943a519d7b13c7d2b573b57a1c45b5cbee9 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/Untitled design (9) (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63a506e67ff868dfaed5b294236d518a234d91c6e0319144c8e8d52d3e201ab8 +size 147774 diff --git a/TL--documentation-new/.gitbook/assets/c (1).png b/TL--documentation-new/.gitbook/assets/c (1).png new file mode 100644 index 0000000000000000000000000000000000000000..39a838fb26e3ac9738f48b41e7003181b768919c --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/c (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9222828eca8cb55cd7d6af08c574f8bd5f71c50d7eb4f58478a24f91193a55c4 +size 125832 diff --git a/TL--documentation-new/.gitbook/assets/g (2).png b/TL--documentation-new/.gitbook/assets/g (2).png new file mode 100644 index 0000000000000000000000000000000000000000..1e9b65b70b96f6065a011a0ef45d5df5c803a73c --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/g (2).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43c415fd6ca8201285ad980f690a65c3f21ae91936009690613e357bd80b13a4 +size 41149 diff --git a/TL--documentation-new/.gitbook/assets/image (10).png b/TL--documentation-new/.gitbook/assets/image (10).png new file mode 100644 index 0000000000000000000000000000000000000000..6df3c3e53ad383011123dd17a2cb8542dd9c1960 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/image (10).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f3d0d83de0d453cb087386c4f9a434774350d4be56d0885efe7627663d7b75a +size 103056 diff --git a/TL--documentation-new/.gitbook/assets/image (11).png b/TL--documentation-new/.gitbook/assets/image (11).png new file mode 100644 index 0000000000000000000000000000000000000000..a7cf667db0e076d55c26fee2b87276ae35341dd3 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/image (11).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2061018f5b31d35535970dba828eac5d3bb2ae0c4759a124ef8c1a913361d2c +size 192931 diff --git a/TL--documentation-new/.gitbook/assets/image (5).png b/TL--documentation-new/.gitbook/assets/image (5).png new file mode 100644 index 0000000000000000000000000000000000000000..4b6e5b0d2b71479713d56da1bacb8c91d92923ca --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/image (5).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26691af349d94b4191b829a832489dca30cac87ecc165dd7a3d17f66fc260d99 +size 86663 diff --git a/TL--documentation-new/.gitbook/assets/image (8).png b/TL--documentation-new/.gitbook/assets/image (8).png new file mode 100644 index 0000000000000000000000000000000000000000..7955a1344776898f6f4e746d735d36cfe3bd8626 --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/image (8).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:155296b07d381796c7013d6c96e922398afe9f5fe4ec23b5bafdf3b56ad86aac +size 81583 diff --git a/TL--documentation-new/.gitbook/assets/image (9).png b/TL--documentation-new/.gitbook/assets/image (9).png new file mode 100644 index 0000000000000000000000000000000000000000..9b7158e62d2fd63081fb7c51bcc92b024250708a --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/image (9).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62989a4c045e2f299e73bcef9a914c36b17edfbc196d4d9b024141254155b4df +size 81515 diff --git a/TL--documentation-new/.gitbook/assets/new (1).png b/TL--documentation-new/.gitbook/assets/new (1).png new file mode 100644 index 0000000000000000000000000000000000000000..b62ea8e3c5937d7f52349d1f2f35f34ea0e3959a --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/new (1).png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f51c30f1f6d6a539123acee4a55a3a5f36676575a716c138a6625fb090c5b07f +size 191392 diff --git a/TL--documentation-new/.gitbook/assets/z.png b/TL--documentation-new/.gitbook/assets/z.png new file mode 100644 index 0000000000000000000000000000000000000000..58a4a6876dfe2bf9ea9c6768ccd5bbcf8164d67e --- /dev/null +++ b/TL--documentation-new/.gitbook/assets/z.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a72698186db5fa994b1fc7acd805511870642dbb23335e459bad4f37130ea2ea +size 36237 diff --git a/TL--documentation-new/README.md b/TL--documentation-new/README.md new file mode 100644 index 0000000000000000000000000000000000000000..0dd85cf490ccabfb970898cc6343402e0a3bbf1f --- /dev/null +++ b/TL--documentation-new/README.md @@ -0,0 +1,15 @@ +--- +cover: .gitbook/assets/Screen-Shot-2021-12-28-at-10-45-33-PM.png +coverY: 0 +--- + +# ๐Ÿ‘‹ Welcome! + +## Welcome aboard! + +Welcome to the Torch Labs Dashboard help center! + +This guide will have answers to 99% of your questions! + + + diff --git a/TL--documentation-new/SUMMARY.md b/TL--documentation-new/SUMMARY.md new file mode 100644 index 0000000000000000000000000000000000000000..1db47329d2b4417e6c1336e2d0411bf406fd85e8 --- /dev/null +++ b/TL--documentation-new/SUMMARY.md @@ -0,0 +1,146 @@ +# Table of contents + +* [๐Ÿ‘‹ Welcome!](README.md) + +## General Settings + +* [๐Ÿ“Š Configuring sales analytics](general-settings/configuring-sales-analytics.md) +* [๐Ÿ’ธ Transactions](general-settings/transactions/README.md) + * [โธ Subscription](general-settings/transactions/subscription.md) +* [๐Ÿงช Transaction status](general-settings/transaction-status.md) +* [โณ Exporting user information](general-settings/exporting-user-information.md) +* [โฌ Exporting user transactions](general-settings/exporting-user-transactions.md) + +## Product Settings + +* [๐Ÿ“Ž Product metadata](product-settings/product-metadata.md) +* [๐Ÿ“ฅ Disabling the product's stock](product-settings/disabling-the-products-stock.md) +* [๐Ÿ“ค Enabling the product's stock](product-settings/enabling-the-products-stock.md) +* [๐Ÿ’ฒ Coupons](product-settings/coupons/README.md) + * [โฐ Non-Limited Coupon](product-settings/coupons/non-limited-coupon.md) + * [๐Ÿ‘ฅ Limited Coupon](product-settings/coupons/limited-coupon.md) +* [๐Ÿชœ Reorder your products](product-settings/reorder-your-products.md) +* [โŒ Deleting a product price](product-settings/deleting-a-product-price.md) +* [๐Ÿ—‘ Deleting an entire product](product-settings/deleting-an-entire-product.md) +* [๐Ÿ’ฐ Change price of a product](product-settings/change-price-of-a-product.md) +* [๐Ÿ“œ Changing Product Description](product-settings/changing-product-description.md) +* [โ™ป Creating a recurring price for a product](product-settings/creating-a-recurring-price-for-a-product.md) +* [๐Ÿ“‘ Changing tab names](product-settings/changing-tab-names.md) + +## Residential Products + +* [โœ… Adding residential products](residential-products/adding-residential-products.md) +* [๐Ÿ‘ฎโ™€ User management](residential-products/user-management.md) +* [โณ View users current balance](residential-products/view-users-current-balance.md) +* [๐Ÿ’ป Updating user's data balance](residential-products/updating-users-data-balance.md) +* [๐Ÿ‘† Top up data manually](residential-products/top-up-data-manually.md) +* [๐ŸŠโ™‚ Residential pools](residential-products/residential-pools.md) +* [โ„น Residential Provider Information](residential-products/residential-provider-information.md) + +## Data Center & Accounts + +* [โœ… Adding data center products](data-center-and-accounts/adding-data-center-products.md) +* [โœ… Adding account products](data-center-and-accounts/adding-account-products.md) +* [๐Ÿ“ค Fulfill manual order](data-center-and-accounts/fulfill-manual-order.md) +* [๐Ÿ”ง Creating a manual release](data-center-and-accounts/creating-a-manual-release.md) +* [๐Ÿค– Creating an automatic release](data-center-and-accounts/creating-an-automatic-release.md) +* [โœ Editing a release](data-center-and-accounts/editing-a-release.md) +* [๐Ÿ›‘ Stopping a release](data-center-and-accounts/stopping-a-release.md) +* [๐Ÿ” Edit and view delivered products](data-center-and-accounts/edit-and-view-delivered-products.md) +* [๐Ÿšง Add stock limit for DC orders](data-center-and-accounts/add-stock-limit-for-dc-orders.md) +* [๐Ÿ’Œ Leave a note on an order](data-center-and-accounts/leave-a-note-on-an-order.md) +* [๐Ÿ—‘ Delete pending a transaction](data-center-and-accounts/delete-pending-a-transaction.md) +* [๐Ÿชœ ISP Expiration Date](data-center-and-accounts/isp-expiration-date.md) +* [โš• Editing incomplete transactions](data-center-and-accounts/editing-incomplete-transactions.md) +* [โš“ Creating Tanmay's ISP API Batch](data-center-and-accounts/creating-tanmays-isp-api-batch.md) +* [๐Ÿ”ฑ Creating Porter Proxies' ISP API Batch](data-center-and-accounts/creating-porter-proxies-isp-api-batch.md) +* [๐Ÿ“‚ Creating manual orders for ISPs / Accounts](data-center-and-accounts/creating-manual-orders-for-isps-accounts.md) + +## โš™ More Settings + +* [๐Ÿ”“ Password page](more-settings/password-page/README.md) + * [๐Ÿ‘ฅ Limited password release](more-settings/password-page/limited-password-release.md) + * [โฐ Non-limited password release](more-settings/password-page/non-limited-password-release.md) +* [๐ŸŽž Transaction discord webhook](more-settings/transaction-discord-webhook.md) +* [๐Ÿ“ฃ Notifications for transactions](more-settings/notifications-for-transactions.md) +* [๐ŸŽฐ Enabling TOS pop-up](more-settings/enabling-tos-pop-up.md) +* [๐ŸŽŸ Enable discord auto join](more-settings/enable-discord-auto-join.md) +* [๐Ÿ›ก Restrict dashboard access](more-settings/restrict-dashboard-access.md) +* [๐Ÿ–‡ Enabling pagination](more-settings/enabling-pagination.md) +* [โ™ฃ Sub Admin Users](more-settings/sub-admin-users/README.md) + * [โ›ณ Permissions](more-settings/sub-admin-users/permissions.md) +* [๐Ÿ˜ Filtering Users](more-settings/filtering-users.md) +* [๐Ÿšก Searching Transactions](more-settings/searching-transactions.md) +* [โœ‚ Adding and Removing ISP API](more-settings/adding-and-removing-isp-api.md) +* [๐Ÿ’ฐ Enabling Stripe Tax](more-settings/enabling-stripe-tax.md) +* [๐ŸŽญ Dashboard UI](more-settings/dashboard-ui/README.md) + * [๐Ÿ” Uploading Primary Logo](more-settings/dashboard-ui/uploading-primary-logo.md) + * [โžฐ Uploading Secondary Logo](more-settings/dashboard-ui/uploading-secondary-logo.md) + * [๐Ÿ“› Updating Company Name](more-settings/dashboard-ui/updating-company-name.md) + * [๐ŸŒ€ Updating Twitter Link](more-settings/dashboard-ui/updating-twitter-link.md) + * [๐Ÿ’ฟ Updating Discord Link](more-settings/dashboard-ui/updating-discord-link.md) + * [๐ŸŒ Updating Theme](more-settings/dashboard-ui/updating-theme.md) + +## Onboarding Guide + +* [โš™ Setting up discord authentication](onboarding-guide/setting-up-discord-authentication.md) +* [โœ… Onboarding a residential product](onboarding-guide/onboarding-a-residential-product.md) +* [๐ŸŒ Access DNS settings](onboarding-guide/access-dns-settings.md) +* [โœˆ Adding Your Site To Your Domain](onboarding-guide/adding-your-site-to-your-domain.md) +* [ใ€ฝ White labeling proxies with your domain](onboarding-guide/white-labeling-proxies-with-your-domain.md) +* [๐Ÿ—ƒ Find Discord ID](onboarding-guide/find-discord-id.md) +* [๐Ÿ’Š Customize dashboard theme](onboarding-guide/customize-dashboard-theme.md) +* [๐Ÿชก Setting Up A Domain](onboarding-guide/setting-up-a-domain.md) +* [๐Ÿ”„ Setting Up A Stripe Account](onboarding-guide/setting-up-a-stripe-account.md) + +## Proxy Masking + +* [โš– Loadbalancer management](proxy-masking/loadbalancer-management.md) +* [๐Ÿ˜ท Proxy Masking Guide](proxy-masking/proxy-masking-guide.md) + +## Customer Dashboard + +* [๐Ÿ›ƒ Custom Pools](customer-dashboard/custom-pools.md) +* [โ™ View Data Usage](customer-dashboard/view-data-usage.md) +* [๐Ÿ–ฑ Access user settings](customer-dashboard/access-user-settings.md) +* [๐ŸŽ› Setting up the Default Country](customer-dashboard/setting-up-the-default-country.md) +* [๐Ÿ Updating Proxy Credentials](customer-dashboard/updating-proxy-credentials.md) +* [๐Ÿง Customer subscription portal](customer-dashboard/customer-subscription-portal.md) +* [๐ŸŽ“ Proxy Generation](customer-dashboard/proxy-generation.md) + +## Errors & FAQ + +* [Stripe Radar](errors-and-faq/stripe-radar.md) +* [How to prevent fraud & Chargebacks](errors-and-faq/how-to-prevent-fraud-and-chargebacks.md) +* [Stripe chargeback protection](errors-and-faq/stripe-chargeback-protection.md) +* [โ” No stripe products are linked error](errors-and-faq/no-stripe-products-are-linked-error.md) +* [โ” Error 400](errors-and-faq/error-400.md) +* [โ” Error 504](errors-and-faq/error-504.md) +* [โ” Bright data, country not displaying correctly when testing](errors-and-faq/bright-data-country-not-displaying-correctly-when-testing.md) +* [โ” Why is the data usage inequal for the same amount of tasks from different providers ?](errors-and-faq/why-is-the-data-usage-inequal-for-the-same-amount-of-tasks-from-different-providers.md) +* [โ” How to prevent fraud](errors-and-faq/how-to-prevent-fraud.md) +* [โ” What happens if someone overuses the data ?](errors-and-faq/what-happens-if-someone-overuses-the-data.md) +* [โ” How to get stripe account ID ?](errors-and-faq/how-to-get-stripe-account-id.md) +* [โ” Is it necessary to add wildcard domain when onboarding ?](errors-and-faq/is-it-necessary-to-add-wildcard-domain-when-onboarding.md) +* [โ” Getting an auth error coming when accessing to user dashboard ?](errors-and-faq/getting-an-auth-error-coming-when-accessing-to-user-dashboard.md) +* [โ” Can the users use the data after the cancellation of the dashboard ?](errors-and-faq/can-the-users-use-the-data-after-the-cancellation-of-the-dashboard.md) +* [โ” Why does the auto join feature on admin dashboard not work?](errors-and-faq/why-does-the-auto-join-feature-on-admin-dashboard-not-work.md) +* [โ” How does ISP expiration date work if ISPs are ordered directly?](errors-and-faq/how-does-isp-expiration-date-work-if-isps-are-ordered-directly.md) +* [โ” What can be done if the Stripe account gets suspended?](errors-and-faq/what-can-be-done-if-the-stripe-account-gets-suspended.md) +* [โ” Why is the customer ISP plan says can not checkout ?](errors-and-faq/why-is-the-customer-isp-plan-says-can-not-checkout.md) +* [โ” How does the auto delivery on proxy site work?](errors-and-faq/how-does-the-auto-delivery-on-proxy-site-work.md) +* [โ” Why is the data usage not the same for the same amount of tasks from different providers ?](errors-and-faq/why-is-the-data-usage-not-the-same-for-the-same-amount-of-tasks-from-different-providers.md) +* [โ” Why is the required region not indicating on the proxies generated by some providers ?](errors-and-faq/why-is-the-required-region-not-indicating-on-the-proxies-generated-by-some-providers.md) +* [โ” How is residential data billed?](errors-and-faq/how-is-residential-data-billed.md) +* [โ” Why is the logo not getting updated and viewed on customer dashboard ?](errors-and-faq/why-is-the-logo-not-getting-updated-and-viewed-on-customer-dashboard.md) +* [โ” What is the ideal size of the logo ?](errors-and-faq/what-is-the-ideal-size-of-the-logo.md) +* [โ” What needs to be done if the proxies are down / failing / not working ?](errors-and-faq/what-needs-to-be-done-if-the-proxies-are-down-failing-not-working.md) +* [โ” Why has the datacenter/accounts batch oversold ?](errors-and-faq/why-has-the-datacenter-accounts-batch-oversold.md) +* [โ” What is proxy Cname ?](errors-and-faq/what-is-proxy-cname.md) +* [โ” Will the ISP product be removed from the dashboard after 30 days ?](errors-and-faq/will-the-isp-product-be-removed-from-the-dashboard-after-30-days.md) +* [โ” Smart proxies not working?](errors-and-faq/smart-proxies-not-working.md) +* [โ” What information does Stripe need to create an account?](errors-and-faq/what-information-does-stripe-need-to-create-an-account.md) +* [โ” How to change URL ?](errors-and-faq/how-to-change-url.md) +* [โ” How to create a coupon for subscription product to apply only for the first month ?](errors-and-faq/how-to-create-a-coupon-for-subscription-product-to-apply-only-for-the-first-month.md) +* [โ” How to fix the subscription portal issue ?](errors-and-faq/how-to-fix-the-subscription-portal-issue.md) +* [โ” Are the products get deleted when changing and syncing a price ?](errors-and-faq/are-the-products-get-deleted-when-changing-and-syncing-a-price.md) diff --git a/TL--documentation-new/customer-dashboard/access-user-settings.md b/TL--documentation-new/customer-dashboard/access-user-settings.md new file mode 100644 index 0000000000000000000000000000000000000000..195fe213d106689b0105589eef5eb63bc67d6daa --- /dev/null +++ b/TL--documentation-new/customer-dashboard/access-user-settings.md @@ -0,0 +1,29 @@ +# ๐Ÿ–ฑ Access user settings + +{% hint style="info" %} +This guide will help you to find the access to Other Setting on User Dashboard. +{% endhint %} + +_Go to User Dashboard and click on the gear icon to find the other settings._ + +
+ +Following are the other settings and click on the link to be directed to relevant guide. + +* Setting up the Default Country + +{% content-ref url="setting-up-the-default-country.md" %} +[setting-up-the-default-country.md](setting-up-the-default-country.md) +{% endcontent-ref %} + +* Updating Proxy Credentials + +{% content-ref url="updating-proxy-credentials.md" %} +[updating-proxy-credentials.md](updating-proxy-credentials.md) +{% endcontent-ref %} + +* Managing Subscription and Billing + +{% content-ref url="customer-subscription-portal.md" %} +[customer-subscription-portal.md](customer-subscription-portal.md) +{% endcontent-ref %} diff --git a/TL--documentation-new/customer-dashboard/custom-pools.md b/TL--documentation-new/customer-dashboard/custom-pools.md new file mode 100644 index 0000000000000000000000000000000000000000..b95a210132fcc7ffc641b0e36150b00b1448915e --- /dev/null +++ b/TL--documentation-new/customer-dashboard/custom-pools.md @@ -0,0 +1,8 @@ +# ๐Ÿ›ƒ Custom Pools + +This feature will help you to generate specific (selected) countries at the same time when generating proxies. + +1. Go to Customer dashboard and select countries to generate the proxies from. For an example choosing United States , United Kingdom , Germany and United Arab Emirates. +2. Then generate the proxies (i.e. Generate 100 proxies and customers get 25 each from the selected countries) + +
diff --git a/TL--documentation-new/customer-dashboard/customer-subscription-portal.md b/TL--documentation-new/customer-dashboard/customer-subscription-portal.md new file mode 100644 index 0000000000000000000000000000000000000000..61b2e954fbea379f0dc093552cd563c0b9cec2b1 --- /dev/null +++ b/TL--documentation-new/customer-dashboard/customer-subscription-portal.md @@ -0,0 +1,29 @@ +# ๐Ÿง Customer subscription portal + +{% hint style="info" %} +This guide will help you set up subscription management within stripe and will help you customize the functionality of the customer portal. +{% endhint %} + +Our customer-facing dashboard has a new settings page where customers can now see their Stripe billing portal. + +{% content-ref url="access-user-settings.md" %} +[access-user-settings.md](access-user-settings.md) +{% endcontent-ref %} + +This is only visible if the customer has bought a recurring product. In the Stripe billing portal, they can cancel their subscription or update their billing details along with many other settings. + +![](<../.gitbook/assets/Screen Shot 2022-06-26 at 1.05.05 PM (1).png>) โžก๏ธ ![](<../.gitbook/assets/Screen Shot 2022-06-26 at 1.05.10 PM.png>) + + + +In Stripe, you can customize the billing portal so you can enable or disable the ability for a customer to cancel their recurring product by themself. You can also add an option to pause and unpause the billing as well. Below you can see all the available settings you can customize to your liking. + +To manage the billing settings you can do it through the following link: [https://dashboard.stripe.com/settings/billing/portal](https://dashboard.stripe.com/settings/billing/portal) + + + +Available Billing Options: + + + +![](<../.gitbook/assets/Screen Shot 2022-06-26 at 1.00.36 PM.png>) diff --git a/TL--documentation-new/customer-dashboard/proxy-generation.md b/TL--documentation-new/customer-dashboard/proxy-generation.md new file mode 100644 index 0000000000000000000000000000000000000000..5cdcac4b6c67471867cb25bd36d6d20b0649ca43 --- /dev/null +++ b/TL--documentation-new/customer-dashboard/proxy-generation.md @@ -0,0 +1,47 @@ +# ๐ŸŽ“ Proxy Generation + +{% hint style="info" %} +This section will guide you regarding the options and functions available on user dashboard when generating proxies. + +Our dashboard provides customers with a range of options for generating different formats, which is great for flexibility. Additionally, the ability to target proxies by country, state, and city allows customers to optimize the proxy usage for specific geographic locations. This can be particularly useful for businesses that have a strong local presence and need to gather data from specific regions. Overall, these features provide customers with greater control and customization options, which can ultimately lead to more efficient and effective use of proxies. +{% endhint %} + +1. Go to User Dashboard + +
+ +2\. Click on the drop down of Proxy Pool and select the required provider. + +
+ +3\. Select the Proxy type (i.e. Sticky or Rotating) + +
+ +4\. Then enter the number of Proxies to be generated. + +
+ +5\. Select the SSL option. (This option is still available for Packetstream / Basic proxies only) Selecting _Yes_ would make you have proxies with a secure session where the proxies includes http / https in the URL domain. + +
+ +6\. Select the country. Now you have the ability to choose multiple countries and generate custom pools. + +
+ +6.1 If you select the country as USA (United States of America) then you get the option of clicking on _Advance Settings_ only for Oxylabs , Smart and IPRoyal. + +
+ +6.1.1 If you select IPRoyal as the Proxy pool and select the country as USA, it is able to generate state level proxies by clicking _Advance settings._ + +
+ +6.1.2 If you select Oxylabs or Smart as the Proxy pool and select the country as USA, it is able to generate either state level and city level proxies by clicking _Advance settings._ But it is not possible to select both state and city. Once you select the State, automatically the city selection gets disabled and vice versa. + +
+ +7\. Once all the selections are done, click _Generate._ + +
diff --git a/TL--documentation-new/customer-dashboard/setting-up-the-default-country.md b/TL--documentation-new/customer-dashboard/setting-up-the-default-country.md new file mode 100644 index 0000000000000000000000000000000000000000..1e810aca836a0d934e9c77d43ec23f55212eb158 --- /dev/null +++ b/TL--documentation-new/customer-dashboard/setting-up-the-default-country.md @@ -0,0 +1,16 @@ +# ๐ŸŽ› Setting up the Default Country + +{% hint style="info" %} +This guide will help you to set up the default country of the User Dashboard. +{% endhint %} + +1. First you need to access the user settings + +{% content-ref url="access-user-settings.md" %} +[access-user-settings.md](access-user-settings.md) +{% endcontent-ref %} + +1. _Go to User Dashboard and click on the gear icon._ +2. _Select the preferred country as the default country by clicking the dropdown menu._ + +
diff --git a/TL--documentation-new/customer-dashboard/updating-proxy-credentials.md b/TL--documentation-new/customer-dashboard/updating-proxy-credentials.md new file mode 100644 index 0000000000000000000000000000000000000000..e454d79d3a047d902b35f8d0cd2306b15b815dd4 --- /dev/null +++ b/TL--documentation-new/customer-dashboard/updating-proxy-credentials.md @@ -0,0 +1,25 @@ +# ๐Ÿ Updating Proxy Credentials + +{% hint style="info" %} +This guide will help you to update the credentials of proxies. +{% endhint %} + +{% hint style="info" %} +This function only works for Oxylabs & Smart Proxies. +{% endhint %} + +1. First you need to access the user settings + +{% content-ref url="access-user-settings.md" %} +[access-user-settings.md](access-user-settings.md) +{% endcontent-ref %} + +2\. Click the refreshing sign next to Update Proxy Credentials. + +
+ +3\. Do not exit the page till you see "Successfully updated Proxy Credentials" + +
+ +> _Then you can see the username and password of the proxies are changed accordingly when you generate new set of proxies._ diff --git a/TL--documentation-new/customer-dashboard/view-data-usage.md b/TL--documentation-new/customer-dashboard/view-data-usage.md new file mode 100644 index 0000000000000000000000000000000000000000..df803168f629660cdb46eda1850c999ec64fec2a --- /dev/null +++ b/TL--documentation-new/customer-dashboard/view-data-usage.md @@ -0,0 +1,28 @@ +# โ™ View Data Usage + +{% hint style="info" %} +This guide will help you to view the total usage of different products on user dashboard. +{% endhint %} + +1. Go to User dashboard and select the product you want to check the data usage + +
+ +2\. Click _**View Data Usage**_ + +
+ +_The data usage will be indicated as follows_ + +
+ +3\. Only on Oxylabs (Elite) you can view the day by day usage for one month by clicking _**View Total Usage**_. + +
+ +_Day by day usage will be displayed as follows_ + +
+ + + diff --git a/TL--documentation-new/data-center-and-accounts/add-stock-limit-for-dc-orders.md b/TL--documentation-new/data-center-and-accounts/add-stock-limit-for-dc-orders.md new file mode 100644 index 0000000000000000000000000000000000000000..a465ed0a9a31c4fde60d8565a1892802ff91b007 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/add-stock-limit-for-dc-orders.md @@ -0,0 +1,21 @@ +# ๐Ÿšง Add stock limit for DC orders + +{% hint style="info" %} +Sometimes, you might receive overwhelming orders which means more than what you have in stock and this will lead to inappropriate refunds and cacellations, To avoid such situations you can limit the orders as per available stock. +{% endhint %} + +1. Go to Datacenter in the dashboard and switch to manual as shown below. + +![](<../.gitbook/assets/1 (62) (5).png>) + +**2.** Then edit batch. + +![](<../.gitbook/assets/1 (63) (8).png>) + +**3.** Then enable the stock limit. + +![](<../.gitbook/assets/1 (64) (4).png>) + +**4.** Here you can give the stock limit then click confirm and save. + +![](<../.gitbook/assets/1 (65) (1).png>) diff --git a/TL--documentation-new/data-center-and-accounts/adding-account-products.md b/TL--documentation-new/data-center-and-accounts/adding-account-products.md new file mode 100644 index 0000000000000000000000000000000000000000..3af0e0f1f2480ea5a4e0571a4e97828f20db097a --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/adding-account-products.md @@ -0,0 +1,105 @@ +# โœ… Adding account products + +{% hint style="info" %} +The steps for an Account Product is the same as below. However, you will need to do the steps in the _Accounts_ tab instead of the _Datacenter_ tab. +{% endhint %} + +{% hint style="info" %} +If you are going to update / edit products When the proxies are active , editing product may cause to delete the stock in the batches. Therefore please make sure to back up them before editing the products. + +This only affects manual and automatic mode whereas it doesn't affect on API mode. +{% endhint %} + +{% content-ref url="../product-settings/product-metadata.md" %} +[product-metadata.md](../product-settings/product-metadata.md) +{% endcontent-ref %} + +{% hint style="success" %} +Any product can have two types of prices: + +1. One-time - Customer is billed once +2. Recurring - Customer is billed on a recurring basis (eg: Monthly) +{% endhint %} + +1\. Firstly, Log in to the Stripe Account. + +![](<../.gitbook/assets/Untitled design (1) (3).png>) + +2\. Click on the _**Products**_ tab found on the right navigation pane of the _Stripe Dashboar_d. + +![](<../.gitbook/assets/Untitled design (2) (10).png>) + +3\. Next _**Add Products**_ as data center plan. + +![](<../.gitbook/assets/Untitled design (3) (10).png>) + +4\. Then name your product. + +{% hint style="info" %} +The name you enter here is what the dashboard will call the product. +{% endhint %} + +![](<../.gitbook/assets/1 (35) (1).png>) + +5\. Also set the price for your product. + +{% hint style="info" %} +This is the price that customers will be paying for your product +{% endhint %} + +![](<../.gitbook/assets/Untitled design (5) (6).png>) + +6\. Click _**One Time**_ or _**Recurring**_ for the pricing section. + +More info regarding recurring pricing can be found below: + +![](<../.gitbook/assets/Untitled design (6) (2).png>) + +7\. Please repeat this process to add another price for the same product. + +![](<../.gitbook/assets/Untitled design (7) (2).png>) + +8\. After adding all your prices, click _**Additional Options**_. + +![](<../.gitbook/assets/1 (44).png>) + +9\. Then add Metadata tags we have provided for the _**MetaData**_ section that can be found below. Then save the product. + +{% hint style="info" %} +Copy and Paste from the below to omit any errors. +{% endhint %} + +The first field should have `torchlabs_product` + +The next field is where we capture if you are making a daily/weekly/monthly product. Therefore, we use the folowing identifiers. (Each product can have only one Identifier, so if you want to make weekly and monthly DC plans, you will need to make two individual products) + +`torchlabs_accounts` + +![](<../.gitbook/assets/1 (58).png>) + +10\. Here you can view all the prices created, And click on a price. + +![](<../.gitbook/assets/1 (45).png>) + +11\. Next, we add Meta data to each price. This helps us determine how many proxies are to be delivered at each price point. The first identifier that you need to enter is `amount` + +{% hint style="info" %} +In this example, there will be 10 proxies being delivered to the customer. +{% endhint %} + +![](<../.gitbook/assets/1 (43) (1).png>) + +12\. Now go-to products and now we are done with our first product. + +![](<../.gitbook/assets/1 (42).png>) + +13\. Then go back to your dashboard and choose the product. + +![](<../.gitbook/assets/1 (75).png>) + +14\. Then sync with stripe. + +![](<../.gitbook/assets/Screenshot (966).png>) + +15\. If everything goes well you should see your plans ,You can repeat this process to create the other Data Center and ISP products. + diff --git a/TL--documentation-new/data-center-and-accounts/adding-data-center-products.md b/TL--documentation-new/data-center-and-accounts/adding-data-center-products.md new file mode 100644 index 0000000000000000000000000000000000000000..aeab528ccea4f4552866c119ab9a465823321a69 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/adding-data-center-products.md @@ -0,0 +1,116 @@ +# โœ… Adding data center products + +{% hint style="info" %} +This guide will walk you through step by step process of adding data center products to your stripe. +{% endhint %} + +{% hint style="info" %} +If you are going to update / edit products When the proxies are active , editing product may cause to delete the stock in the batches. Therefore please make sure to back up them before editing the products. + +This only affects manual and automatic mode whereas it doesn't affect on API mode. +{% endhint %} + +{% content-ref url="../product-settings/product-metadata.md" %} +[product-metadata.md](../product-settings/product-metadata.md) +{% endcontent-ref %} + +{% hint style="success" %} +Any product can have two types of prices: + +1. One-time - Customer is billed once +2. Recurring - Customer is billed on a recurring basis (eg: Monthly) +{% endhint %} + + + +1\. Firstly, Log in to the Stripe Account. + +![](<../.gitbook/assets/Untitled design (1) (3).png>) + +2\. Click on the _**Products**_ tab found on the right navigation pane of the _Stripe Dashboar_d. + +![](<../.gitbook/assets/Untitled design (2) (10).png>) + +3\. Next _**Add Product**_ as data center plan. + +![](<../.gitbook/assets/Untitled design (3) (10).png>) + +4\. Then name your product. + +{% hint style="info" %} +The name you enter here is what the dashboard will call the product. +{% endhint %} + +![](<../.gitbook/assets/1 (35) (1).png>) + +5\. Also set the price for your product. + +{% hint style="info" %} +This is the price that customers will be paying for your product +{% endhint %} + +![](<../.gitbook/assets/Untitled design (5) (6).png>) + +6\. Click _**One Time**_ or _**Recurring**_ for the pricing section. + +More info regarding recurring pricing can be found below: + +{% content-ref url="../product-settings/creating-a-recurring-price-for-a-product.md" %} +[creating-a-recurring-price-for-a-product.md](../product-settings/creating-a-recurring-price-for-a-product.md) +{% endcontent-ref %} + +![](<../.gitbook/assets/Untitled design (6) (2).png>) + +7\. Please repeat this process to add another price for the same product. + +![](<../.gitbook/assets/Untitled design (7) (2).png>) + +8\. After adding all your prices, click _**Additional Options**_. + +![](<../.gitbook/assets/1 (44).png>) + +9\. Then add Metadata tags we have provided for the _**MetaData**_ section that can be found below. Then save the product. + +{% hint style="info" %} +Copy and Paste from the below to omit any errors. +{% endhint %} + +The first field should have `torchlabs_product` + +The next field is where we capture if you are making a daily/weekly/monthly product. Therefore, we use the following identifiers. (Each product can have only one Identifier, so if you want to make weekly and monthly DC plans, you will need to make two individual products) + +`torchlabs_datacenter_daily` + +`torchlabs_datacenter_weekly` + +`torchlabs_datacenter_monthly` + +& more products can be added by looking at our Meta Data section + +![](../.gitbook/assets/image.png) + +10\. Here you can view all the prices created, And click on a price. + +![](<../.gitbook/assets/1 (45) (1).png>) + +11\. Next, we add Meta data to each price. This helps us determine how many proxies are to be delivered at each price point. The first identifier that you need to enter is `amount` + +{% hint style="info" %} +In this example, there will be 10 proxies being delivered to the customer +{% endhint %} + +![](<../.gitbook/assets/image (10).png>) + +12\. Now go to products and we are done with our first product. + +![](<../.gitbook/assets/1 (42) (1) (1).png>) + +13\. Then go back to your dashboard and choose the product type we just set up and edit it. + +![](<../.gitbook/assets/1 (75) (1).png>) + +14\. Next, click Sync with Stripe. Once the sync is completed you should see your plans. + +![](<../.gitbook/assets/1 (41) (1) (2) (1).png>) + +15\. You can repeat this process to create the other Data Center and ISP products. diff --git a/TL--documentation-new/data-center-and-accounts/creating-a-manual-release.md b/TL--documentation-new/data-center-and-accounts/creating-a-manual-release.md new file mode 100644 index 0000000000000000000000000000000000000000..784582afd7ee45605655d149439a7a6ad059f446 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/creating-a-manual-release.md @@ -0,0 +1,39 @@ +# ๐Ÿ”ง Creating a manual release + +{% hint style="info" %} +There are two types release auto and manual, In order to create manual releases please check this guide. +{% endhint %} + +{% hint style="info" %} +If you want to stop release in a manual release follow this link. +{% endhint %} + +{% content-ref url="stopping-a-release.md" %} +[stopping-a-release.md](stopping-a-release.md) +{% endcontent-ref %} + +1. Go to dashboard then data center and click the drop down to choose the Manual. + +![](<../.gitbook/assets/1 (71) (1).png>) + +2\. Click New Batch + +![](<../.gitbook/assets/1 (72) (4).png>) + +3\. Once the pop up comes you can add a stock limit or confirm the order. + +{% content-ref url="add-stock-limit-for-dc-orders.md" %} +[add-stock-limit-for-dc-orders.md](add-stock-limit-for-dc-orders.md) +{% endcontent-ref %} + +![](<../.gitbook/assets/1 (62) (1).png>) + +4\. Click launch to make sure the batches are active. + +![](<../.gitbook/assets/1 (63) (2).png>) + +You have the option of adding an expiration date on ISPs and please find the following guide. + +{% content-ref url="isp-expiration-date.md" %} +[isp-expiration-date.md](isp-expiration-date.md) +{% endcontent-ref %} diff --git a/TL--documentation-new/data-center-and-accounts/creating-an-automatic-release.md b/TL--documentation-new/data-center-and-accounts/creating-an-automatic-release.md new file mode 100644 index 0000000000000000000000000000000000000000..62ccf03f9922d4eadd458d787ac62ad564490b8b --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/creating-an-automatic-release.md @@ -0,0 +1,23 @@ +# ๐Ÿค– Creating an automatic release + +{% hint style="info" %} +There are two types release auto and manual, In order to create auto releases please check this guide. +{% endhint %} + +1. Go to dashboard then datacenter and click the drop-down to choose the Automatic. + +![](<../.gitbook/assets/1 (73) (5).png>) + +2\. Next, click on new batch. + +![](<../.gitbook/assets/1 (72) (2).png>) + +3\. Add your proxies here click confirm and launch + +![](<../.gitbook/assets/Screenshot (970).png>) + +You have the option of adding an expiration date on ISPs and please find the following guide. + +{% content-ref url="isp-expiration-date.md" %} +[isp-expiration-date.md](isp-expiration-date.md) +{% endcontent-ref %} diff --git a/TL--documentation-new/data-center-and-accounts/creating-manual-orders-for-isps-accounts.md b/TL--documentation-new/data-center-and-accounts/creating-manual-orders-for-isps-accounts.md new file mode 100644 index 0000000000000000000000000000000000000000..12f1d5893f0a35231d6aaf99cf0b5a9cba5cc7e6 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/creating-manual-orders-for-isps-accounts.md @@ -0,0 +1,46 @@ +# ๐Ÿ“‚ Creating manual orders for ISPs / Accounts + +{% hint style="info" %} +This section will guide you on how to create a manual order for ISPs/ Accounts. This is similar to add/ remove data to people using the admin dashboard for residential providers. +{% endhint %} + +{% hint style="info" %} +Internal notes are only visible by admins and not the users +{% endhint %} + +1. Go to Datacenter / Account tab on admin dashboard + +
+ +2\. Select _Create Order_ + +
+ +3\. Select the user that the accounts / ISPs to be added for + +
+ +4\. Select the product that needs to be added + +
+ +5\. Paste the ISPs / Account list here + +
+ +6\. Set the expiration date or the number of days from creation date to expiration date for the pasted list. + +
+ +7\. Admin can add an internal note here as required + +
+ +7.1 That internal note would be displayed in Transactions tab under payment sub-tab + +
+ +8. Tick confirm and then select add. + +
+ diff --git a/TL--documentation-new/data-center-and-accounts/creating-porter-proxies-isp-api-batch.md b/TL--documentation-new/data-center-and-accounts/creating-porter-proxies-isp-api-batch.md new file mode 100644 index 0000000000000000000000000000000000000000..9cdbe6191fc5f258db36161b7668304b8416921d --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/creating-porter-proxies-isp-api-batch.md @@ -0,0 +1,29 @@ +# ๐Ÿ”ฑ Creating Porter Proxies' ISP API Batch + +{% hint style="info" %} +This section will guide you on how to create an ISP API batch for a registered APIs. Each ISP API can be assigned to one product / batch only. In this way customers can have multiple APIs / Products. +{% endhint %} + +1. Go to _Datacenter_ tab on Admin Dashboard. + +
+ +2\. Click on the dropdown list before new batch. + +
+ +3\. Select the Registered ISP from the list and click on New Batch. **** + +You can select the API only if you have already registered an API using the following guide. + +{% content-ref url="../more-settings/adding-and-removing-isp-api.md" %} +[adding-and-removing-isp-api.md](../more-settings/adding-and-removing-isp-api.md) +{% endcontent-ref %} + +If you precisely registered, all the APIs would appear under the dropdown list including _Porter Proxies_. ISP API batch type for all the customers are now shown as Porter Proxies. Accordingly choose the relevant option when creating the new batch. + +At this stage it gives the ability to assign one product / batch and deliver the stock in one batch. + +4\. Now you can add a stock limit and duration for expiration. Then tick confirm and select launch. At this point the combination of the batch has to be equal or more than the stock limit. + +
diff --git a/TL--documentation-new/data-center-and-accounts/creating-tanmays-isp-api-batch.md b/TL--documentation-new/data-center-and-accounts/creating-tanmays-isp-api-batch.md new file mode 100644 index 0000000000000000000000000000000000000000..1337dfaed83d92a0c2a6c494e06c0034410363d1 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/creating-tanmays-isp-api-batch.md @@ -0,0 +1,29 @@ +# โš“ Creating Tanmay's ISP API Batch + +{% hint style="info" %} +This section will guide you on how to create an ISP API batch for a registered APIs in a multiple subnets together and deliver the stock in one batch. +{% endhint %} + +1. Go to _Datacenter_ tab on Admin Dashboard. + +
+ +2\. Click on the dropdown list before new batch. + +
+ +3\. Select the Registered ISP from the list and click on New Batch. **** + +You can select the API only if you have already registered an API using the following guide. + +{% content-ref url="../more-settings/adding-and-removing-isp-api.md" %} +[adding-and-removing-isp-api.md](../more-settings/adding-and-removing-isp-api.md) +{% endcontent-ref %} + +If you precisely registered, all the APIs would appear under the dropdown list including _Custom Proxies_. ISP API batch type for all the customers are now shown as Custom Proxies. Accordingly choose the relevant option when creating the new batch. + +At this stage it gives the ability to combine ISP API / multiple subnets together and deliver the stock in one batch. But to create multiple subnets together there has to be minimum of 2 ISP APIs registered. + +4\. Now you can add a stock limit and duration for expiration. Then tick confirm and select launch. At this point the combination of the batch has to be equal or more than the stock limit. + +
diff --git a/TL--documentation-new/data-center-and-accounts/delete-pending-a-transaction.md b/TL--documentation-new/data-center-and-accounts/delete-pending-a-transaction.md new file mode 100644 index 0000000000000000000000000000000000000000..37d43d0db2386f0d563f22c7ede82ec5fa4bb43f --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/delete-pending-a-transaction.md @@ -0,0 +1,17 @@ +# ๐Ÿ—‘ Delete pending a transaction + +{% hint style="info" %} +To keep the Dashboard clean without pending and unsuccessful orders, It can be deleted as following. +{% endhint %} + +1. Go to your dashboard and click Datacenter. + +![](<../.gitbook/assets/1 (62) (2).png>) + +2\. The transactions that are incomplete you can see delete icon click that. + +![](<../.gitbook/assets/1 (63).png>) + +3\. Confirm and click delete + +![](<../.gitbook/assets/1 (64) (1).png>) diff --git a/TL--documentation-new/data-center-and-accounts/edit-and-view-delivered-products.md b/TL--documentation-new/data-center-and-accounts/edit-and-view-delivered-products.md new file mode 100644 index 0000000000000000000000000000000000000000..1cc435df99921c9a60098c7f73d91b3e5c10a51d --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/edit-and-view-delivered-products.md @@ -0,0 +1,17 @@ +# ๐Ÿ” Edit and view delivered products + +{% hint style="info" %} +If you need to update or view a delivered product, for example, if you missed something or made a mistake, you can do so. Follow the following steps. +{% endhint %} + +1. Go to transactions in your dashboard + +![](<../.gitbook/assets/1 (62) (7).png>) + +2\. Click edit as shown below + +![](<../.gitbook/assets/1 (63) (9).png>) + +3\. Edit the details you want to edit and click confirm save. + +![](<../.gitbook/assets/1 (64) (6).png>) diff --git a/TL--documentation-new/data-center-and-accounts/editing-a-release.md b/TL--documentation-new/data-center-and-accounts/editing-a-release.md new file mode 100644 index 0000000000000000000000000000000000000000..5cf924fd956f2b28880e6149c7bfb596934ba97d --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/editing-a-release.md @@ -0,0 +1,18 @@ +# โœ Editing a release + +{% hint style="info" %} +You are totally eligible to add and edit any releases after it's made, In order to edit or add a release check this guide. +{% endhint %} + +![](<../.gitbook/assets/1 (64) (5).png>) + +2\. Disable to add proxies + +![](<../.gitbook/assets/1 (66) (2).png>) + +3\. Add proxies here, Confirm and Launch + +![](<../.gitbook/assets/1 (65) (3).png>) + + + diff --git a/TL--documentation-new/data-center-and-accounts/editing-incomplete-transactions.md b/TL--documentation-new/data-center-and-accounts/editing-incomplete-transactions.md new file mode 100644 index 0000000000000000000000000000000000000000..85d08383bc5af11162024907f5581c245f13dfd3 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/editing-incomplete-transactions.md @@ -0,0 +1,31 @@ +# โš• Editing incomplete transactions + +{% hint style="info" %} +This guide will help you to edit the incomplete transactions in Datacenter and Accounts tabs. +{% endhint %} + +> Please refer to the transaction types to have a further understanding regarding incomplete transactions. + +{% content-ref url="../general-settings/transaction-status.md" %} +[transaction-status.md](../general-settings/transaction-status.md) +{% endcontent-ref %} + +1. Go to Datacenter / Accounts tab on Admin Dashboard. + +
+ +2\. Select the incomplete transaction and click on the pencil icon before the product type with reference to that particular transaction. + +
+ +3\. Then you can edit the proxies either by editing them or replacing with new ones. + +
+ +4\. Thereafter you can set an expiration date and time. + +
+ +5\. At last tick _Confirm_ and click save. + +
diff --git a/TL--documentation-new/data-center-and-accounts/fulfill-manual-order.md b/TL--documentation-new/data-center-and-accounts/fulfill-manual-order.md new file mode 100644 index 0000000000000000000000000000000000000000..5bd63bf3706f187329d964e5996de1e73b8e55f9 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/fulfill-manual-order.md @@ -0,0 +1,14 @@ +# ๐Ÿ“ค Fulfill manual order + +{% hint style="info" %} +If you have given manual settings instead of Auto then each order has to be fulfilled manually. This guide will show you how to full manual order. +{% endhint %} + +1. Go to the data center tab + +![](<../.gitbook/assets/Untitled design (9) (4).png>) + +2\. Here click on **Fulfill Now** and paste your list of proxies. + +![](<../.gitbook/assets/Untitled design (11) (6).png>) + diff --git a/TL--documentation-new/data-center-and-accounts/isp-expiration-date.md b/TL--documentation-new/data-center-and-accounts/isp-expiration-date.md new file mode 100644 index 0000000000000000000000000000000000000000..b750983c5ec45b21ade329b07c940702498d8e07 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/isp-expiration-date.md @@ -0,0 +1,29 @@ +# ๐Ÿชœ ISP Expiration Date + +{% hint style="info" %} +This guide will help you to add an expiring date for the automatically and manually generated ISPs. +{% endhint %} + +1. Go to admin dashboard and the click on _**Datacenter**_ tab + +
+ +2\. Select the mode of release from the dropdown list of Automatic and Manual + +
+ +#### Automatic Release + +Once you update the IPs then you can select the expiry date of the IPs as you with along with the time depending on the product. + +
+ +#### Manual Release + +Here you have the option of setting the expiry date along with the time depending on the product. + +
+ +_Expiry date of the orders are displayed on the User Dashboard as follows_ + +
diff --git a/TL--documentation-new/data-center-and-accounts/leave-a-note-on-an-order.md b/TL--documentation-new/data-center-and-accounts/leave-a-note-on-an-order.md new file mode 100644 index 0000000000000000000000000000000000000000..1f3c7e502ea6e92ad2c0d232bc1e9148726c2db4 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/leave-a-note-on-an-order.md @@ -0,0 +1,14 @@ +# ๐Ÿ’Œ Leave a note on an order + +{% hint style="info" %} +If you want to leave a Thank you note or similar note to your delivered order, Please follow the following steps. +{% endhint %} + +1. Click fulfil now as shown below. + +![](<../.gitbook/assets/1 (63) (6).png>) + +2\. Edit the list or note then click confirm and save. + +![](<../.gitbook/assets/1 (62) (6).png>) + diff --git a/TL--documentation-new/data-center-and-accounts/stopping-a-release.md b/TL--documentation-new/data-center-and-accounts/stopping-a-release.md new file mode 100644 index 0000000000000000000000000000000000000000..70534aa1ea9517f40150234e6cd15c3375abe2b9 --- /dev/null +++ b/TL--documentation-new/data-center-and-accounts/stopping-a-release.md @@ -0,0 +1,9 @@ +# ๐Ÿ›‘ Stopping a release + +{% hint style="info" %} +The release can be stopped with simple steps, In order to stop a release follow this guide. +{% endhint %} + +1. Go to the datacenter tab and click on the dissabled toggle to disable the product. + +![](<../.gitbook/assets/1 (71).png>) diff --git a/TL--documentation-new/errors-and-faq/are-the-products-get-deleted-when-changing-and-syncing-a-price.md b/TL--documentation-new/errors-and-faq/are-the-products-get-deleted-when-changing-and-syncing-a-price.md new file mode 100644 index 0000000000000000000000000000000000000000..53dd27750266613632c46f110cf78d007d041ee1 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/are-the-products-get-deleted-when-changing-and-syncing-a-price.md @@ -0,0 +1,7 @@ +# โ” Are the products get deleted when changing and syncing a price ? + +You have to take a backup before syncing a product. Because if you have a batch that is active and you sync a product, then the batch will stop. + +
+ +This happens because the price is now different and any changes done on stripe and synced the batch will reset because the batch was set for the old product. So you need always make sure to take a backup of your batch before changing a price. diff --git a/TL--documentation-new/errors-and-faq/bright-data-country-not-displaying-correctly-when-testing.md b/TL--documentation-new/errors-and-faq/bright-data-country-not-displaying-correctly-when-testing.md new file mode 100644 index 0000000000000000000000000000000000000000..be950c5c401072028c1d37a0d08d2bf9666f0f96 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/bright-data-country-not-displaying-correctly-when-testing.md @@ -0,0 +1,6 @@ +# โ” Bright data, country not displaying correctly when testing + +* With bright the way it works is that there is a main server that accepts the requests coming to the proxies first. This server then routes the traffic to the proxies in the correct region. Like most people who have a plan with bright, they set up their servers in the US to accept the initial traffic. Some bots/proxy testers will show that the proxies are pinning in the US no matter what region they generate because they are just pining the proxies and not actually creating a request using the proxies. In reality the actually proxy is going to be the correct region. So it will still work during geo locking and all during drops. +* Anyway the proxies actually work regardless of what any tester says the region is. +* To test accurately to see which country the proxy is pinging from, please login to chrome using the proxy by following this guide: [https://oxylabs.io/blog/how-to-set-up-a-chrome-proxy](https://oxylabs.io/blog/how-to-set-up-a-chrome-proxy) +* Next, please visit this link to verify what country your proxy is from: [https://lumtest.com/myip.json](https://lumtest.com/myip.json) diff --git a/TL--documentation-new/errors-and-faq/can-the-users-use-the-data-after-the-cancellation-of-the-dashboard.md b/TL--documentation-new/errors-and-faq/can-the-users-use-the-data-after-the-cancellation-of-the-dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..c88b5f2efc9ced56c3cde0e8aef60fe4fff964d7 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/can-the-users-use-the-data-after-the-cancellation-of-the-dashboard.md @@ -0,0 +1,3 @@ +# โ” Can the users use the data after the cancellation of the dashboard ? + +The customers can use the dashboard until the subscription is ended. So if they cancel and they have more days left before the next billing cycle, the dashboard will be online till then. The proxies will only be accessible during this time. If the customer wants their users to still be able to use their proxies, they should continue for an extra month with the subscription so their users can finish their proxy data. diff --git a/TL--documentation-new/errors-and-faq/error-400.md b/TL--documentation-new/errors-and-faq/error-400.md new file mode 100644 index 0000000000000000000000000000000000000000..3c2744687c2013fa5381cbb584c0679873e70e8c --- /dev/null +++ b/TL--documentation-new/errors-and-faq/error-400.md @@ -0,0 +1,24 @@ +--- +description: >- + This guide will make you understand the reasons for getting this error + message. +--- + +# โ” Error 400 + +Please follow the following steps to address the error as following reasons are the cause of this error. + +1. First of all check whether the details are added under the correct stripe account which is Torch Labs. If not select the correct account. + +
+ +2\. Even after adding the products if the customers get the same error then check the metadata entered related to the product. Also make sure there is no spaces before and after the metadata. + +{% content-ref url="../product-settings/product-metadata.md" %} +[product-metadata.md](../product-settings/product-metadata.md) +{% endcontent-ref %} + + + + + diff --git a/TL--documentation-new/errors-and-faq/error-504.md b/TL--documentation-new/errors-and-faq/error-504.md new file mode 100644 index 0000000000000000000000000000000000000000..777b5072dbb9aaf1c36d75bb720a9dab3adde878 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/error-504.md @@ -0,0 +1,7 @@ +# โ” Error 504 + +{% hint style="info" %} +A 504 Gateway Timeout Error means your web server didn't receive a timely response from another server upstream when it attempted to load one of your web pages. +{% endhint %} + +> This error may come because the google dashboard is down or discord API is down. diff --git a/TL--documentation-new/errors-and-faq/getting-an-auth-error-coming-when-accessing-to-user-dashboard.md b/TL--documentation-new/errors-and-faq/getting-an-auth-error-coming-when-accessing-to-user-dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..90419cdcd9bceaa302dd2c79b554c5353874d719 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/getting-an-auth-error-coming-when-accessing-to-user-dashboard.md @@ -0,0 +1,5 @@ +# โ” Getting an auth error coming when accessing to user dashboard ? + +Invalid OAuth error appears when you have missed one step while completing the onboarding process. Please refer to the following guide and complete it. + +[https://docs.torchlabs.xyz/onboarding-guide/setting-up-discord-authentication](https://docs.torchlabs.xyz/onboarding-guide/setting-up-discord-authentication) diff --git a/TL--documentation-new/errors-and-faq/how-does-isp-expiration-date-work-if-isps-are-ordered-directly.md b/TL--documentation-new/errors-and-faq/how-does-isp-expiration-date-work-if-isps-are-ordered-directly.md new file mode 100644 index 0000000000000000000000000000000000000000..f05d03d5418bfe60cc8422bbe97056ac859e2bde --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-does-isp-expiration-date-work-if-isps-are-ordered-directly.md @@ -0,0 +1,15 @@ +# โ” How does ISP expiration date work if ISPs are ordered directly? + +In terms of expiration, if you buy monthly ISPs from us they last 30 days. So from the moment we deliver them to you in the ticket that's when the clock starts. So you should deliver them to your customers the same day we deliver to you so the customers will also still get 30 days. + +\ +For an example: + +* Sneaker release on 25th October +* then You should start taking pre orders on 20th -23rd October. +* you tell us you need ISPs on 23rd right after you close orders and you inform us the total amount customers have ordered. For example lets say 100 in total. +* Then within 24 hours we will get you the 100 ISPs and ping you in the ticket +* then on the 24th of October you deliver all the ISPs to your customers directly via the dashboard. +* Now they are ready for the big release on the 25th October. + +this is how most customers do it. diff --git a/TL--documentation-new/errors-and-faq/how-does-the-auto-delivery-on-proxy-site-work.md b/TL--documentation-new/errors-and-faq/how-does-the-auto-delivery-on-proxy-site-work.md new file mode 100644 index 0000000000000000000000000000000000000000..037b4fbde2f57dd109765663dc89a61026f70d30 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-does-the-auto-delivery-on-proxy-site-work.md @@ -0,0 +1,3 @@ +# โ” How does the auto delivery on proxy site work? + +Once you have the ISPs you just upload them to the dashboard. For example, if you are doing automatic fulfillment you would ideally know your customers and how much demand you have. So lets say you want to restock 1000 ISPs, you load the 1000 in auto mode and just forget about it. As orders come in from customers, they can buy the product as long as it is not OOS (the list you uploaded is not over). If you don't know the demand and you like to sort of do like a preorder method then we recommend using our manual mode. In manual, you would take pre orders for a few days and close the product by making it OOS and once you buy the product from the supplier you can fulfill all the orders that you received during the pre order period. The benefit of this is you get cash up front from your customers before you pay your supplier. diff --git a/TL--documentation-new/errors-and-faq/how-is-residential-data-billed.md b/TL--documentation-new/errors-and-faq/how-is-residential-data-billed.md new file mode 100644 index 0000000000000000000000000000000000000000..350212ebf87b23c85428989109412480f9a107b0 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-is-residential-data-billed.md @@ -0,0 +1,3 @@ +# โ” How is residential data billed? + +Every GB you allocate to the customer (customer purchase or manual data updates) not data consumption. At the end of each month you will get an invoice for the data usage. diff --git a/TL--documentation-new/errors-and-faq/how-to-change-url.md b/TL--documentation-new/errors-and-faq/how-to-change-url.md new file mode 100644 index 0000000000000000000000000000000000000000..f4667a198d69483931811bc695821bb74ac82e48 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-to-change-url.md @@ -0,0 +1,5 @@ +# โ” How to change URL ? + +1\. Go to the following guide and whitelabel the proxies with your domain using the guide here: -[ https://docs.torchlabs.xyz/onboarding-guide/white-labeling-proxies-with-your-domain](https://docs.torchlabs.xyz/onboarding-guide/white-labeling-proxies-with-your-domain) + +2\. Send a screenshot of your DNS configuration diff --git a/TL--documentation-new/errors-and-faq/how-to-create-a-coupon-for-subscription-product-to-apply-only-for-the-first-month.md b/TL--documentation-new/errors-and-faq/how-to-create-a-coupon-for-subscription-product-to-apply-only-for-the-first-month.md new file mode 100644 index 0000000000000000000000000000000000000000..53bf97c09cb87ef12554eb9ef09df3e339e91b6b --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-to-create-a-coupon-for-subscription-product-to-apply-only-for-the-first-month.md @@ -0,0 +1,8 @@ +# โ” How to create a coupon for subscription product to apply only for the first month ? + +1. Please go to the product tab of stripe +2. Select coupon +3. Select the required product and fill the relevant details +4. Select _Once_ as the duration + +
diff --git a/TL--documentation-new/errors-and-faq/how-to-fix-the-subscription-portal-issue.md b/TL--documentation-new/errors-and-faq/how-to-fix-the-subscription-portal-issue.md new file mode 100644 index 0000000000000000000000000000000000000000..d6c7ff9d785cae9d10d06e5ec9aae4e988063278 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-to-fix-the-subscription-portal-issue.md @@ -0,0 +1,16 @@ +# โ” How to fix the subscription portal issue ? + +{% hint style="info" %} +When the customers are trying to access the customer portal they may get a white screen or not get the access at all. In such cases please follow the following steps to fix the problem. +{% endhint %} + + + +1. Search `customer portal` and click it. + +
+ +2. Click `Save changes` button + +
+ diff --git a/TL--documentation-new/errors-and-faq/how-to-get-stripe-account-id.md b/TL--documentation-new/errors-and-faq/how-to-get-stripe-account-id.md new file mode 100644 index 0000000000000000000000000000000000000000..e02ebe27b235651c91c0a1abdb23d8141a96ef21 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-to-get-stripe-account-id.md @@ -0,0 +1,11 @@ +# โ” How to get stripe account ID ? + +1. Go to the relevant stripe account +2. You can refer to the following link to find Stripe account ID + +{% embed url="https://dashboard.stripe.com/settings/account" %} + +3\. Click on _copy ID_ to get the stripe ID and then you can paste it anywhere as required. + +

The ID should be on top right

+ diff --git a/TL--documentation-new/errors-and-faq/how-to-prevent-fraud-and-chargebacks.md b/TL--documentation-new/errors-and-faq/how-to-prevent-fraud-and-chargebacks.md new file mode 100644 index 0000000000000000000000000000000000000000..30865dec4f325063a0189b155b9c428639707e3d --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-to-prevent-fraud-and-chargebacks.md @@ -0,0 +1,2 @@ +# How to prevent fraud & Chargebacks + diff --git a/TL--documentation-new/errors-and-faq/how-to-prevent-fraud.md b/TL--documentation-new/errors-and-faq/how-to-prevent-fraud.md new file mode 100644 index 0000000000000000000000000000000000000000..d98ba1ef66a2d90d3345cee93464115151d1e39b --- /dev/null +++ b/TL--documentation-new/errors-and-faq/how-to-prevent-fraud.md @@ -0,0 +1,45 @@ +# โ” How to prevent fraud + +Sadly there seems to be a fraudulent person in the sneaker community running through proxy companies using **STOLEN credit cards**. They have purchased data from a lot of proxy companies in the sneaker space and they use all the data and actual customers end up charging back the transaction. + +Also do not deal with anyone for crypto unless you checked if they are legit! + +Attackers have used multiple discord sometimes even 10 different accounts and bought data in small amounts such as 2GB through multiple days and they will end up buying a lot of data. + +They mainly want Oxylabs, Private, Packet, IProyal + +**IF YOU ARE A VICTIM:** + +1. Immediately refund the purchase +2. Remove all the data from the user +3. Turn on dashboard restricted access +4. Ban the account from the discord server +5. Turn on TOS pop up so that in case of a charge back you can submit that as evidence + +{% hint style="info" %} +You must create a PDF detailing all the sufficient evidence and mapping the customer to the actual charge back. Look at the below PDF to see an example of what we have done in the past. This example PDF has won 99% of all charge back claims. +{% endhint %} + +{% file src="../.gitbook/assets/Chargeback Example Evidence.pdf" %} + +**TO PREVENT FUTURE INCIDENTS:** + +1. Have discord webhook on so you can monitor every purchase directly in discord: https://docs.torchlabs.xyz/more-settings/enabling-the-webhook +2. Restrict dashboard access so only people in your discord server can purchase! This is very important because all the attacks have been from people not in the discord server: https://docs.torchlabs.xyz/more-settings/enabling-the-webhook +3. Use Dyno bot! (https://dyno.gg/manage) Make sure to have autobahn on this will ban any new accounts less than 2 weeks. This prevents burner accounts from joining your server. All these burner accounts are usually fraudulent accounts. + + * To Enabled: https://dyno.gg/manage + * Go to modules + * Search Auto ban + * Create new rule + * Ban based on account age less than 300 hours + + +4. Enable Stripe radar (https://dashboard.stripe.com/settings/radar) and set custom rules + * Blocking suspicious email domains and only allowing standard domains like gmail and hotmail + * Set up blacklisted IPs for previous fraudulent activities + * You can check with stripe for some other good ones + +**PLEASE BE SAFE!** + +Our dashboard has some of the best features to prevent these types of things but ultimately comes down to stripe to stop these transactions. So please watch all your transactions. If you are making more sales than usual this might mean there may be some fraudulent transactions. diff --git a/TL--documentation-new/errors-and-faq/is-it-necessary-to-add-wildcard-domain-when-onboarding.md b/TL--documentation-new/errors-and-faq/is-it-necessary-to-add-wildcard-domain-when-onboarding.md new file mode 100644 index 0000000000000000000000000000000000000000..41d28d12e31a4b3432c3d9b75425c7eb54d8a57c --- /dev/null +++ b/TL--documentation-new/errors-and-faq/is-it-necessary-to-add-wildcard-domain-when-onboarding.md @@ -0,0 +1,5 @@ +# โ” Is it necessary to add wildcard domain when onboarding ? + +If it is for Plan 1 or 2 (with residential products) it is necessary to add wildcard domain + +If it is for Plan 3 or 4 (without residential products) it is not necessary hence filling the wildcard domain can be skipped. diff --git a/TL--documentation-new/errors-and-faq/no-stripe-products-are-linked-error.md b/TL--documentation-new/errors-and-faq/no-stripe-products-are-linked-error.md new file mode 100644 index 0000000000000000000000000000000000000000..f90d6d00e86ae5c7e1700b8efc2f5f7e0021b3e1 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/no-stripe-products-are-linked-error.md @@ -0,0 +1,30 @@ +--- +description: >- + This guide will make you understand the reasons for getting this error + message. +--- + +# โ” No stripe products are linked error + +Please follow the following steps to address the error. + +1. First of all check whether the details are added under the correct stripe account which is Torch Labs. If not select the correct account. + +
+ +2\. Then check whether the stripe set up is completed. If not please complete the stripe set up. + +3\. Check whether you have added products if not add products on stripe by clicking "Add Product" + +
+ +3\. Even after adding the products if the customers get the same error then check the metadata entered related to the product. Also make sure there is no spaces before and after the metadata. Further check whether the metadata is entered under the correct field. + +{% content-ref url="../product-settings/product-metadata.md" %} +[product-metadata.md](../product-settings/product-metadata.md) +{% endcontent-ref %} + + + + + diff --git a/TL--documentation-new/errors-and-faq/smart-proxies-not-working.md b/TL--documentation-new/errors-and-faq/smart-proxies-not-working.md new file mode 100644 index 0000000000000000000000000000000000000000..eea04c476997e803e315764e5adeec2ac64b53da --- /dev/null +++ b/TL--documentation-new/errors-and-faq/smart-proxies-not-working.md @@ -0,0 +1,8 @@ +# โ” Smart proxies not working? + +There are few reasons that smart proxies might not work + +1. Customer might not have data +2. Their order has failed - they haven't received their data +3. They may be out of data - not having enough data +4. They may be testing on googe. Smart proxy does not allow testing on google therefore please ask the customers to test the proxies on a website like Footlocker. diff --git a/TL--documentation-new/errors-and-faq/stripe-chargeback-protection.md b/TL--documentation-new/errors-and-faq/stripe-chargeback-protection.md new file mode 100644 index 0000000000000000000000000000000000000000..ff4d83b7aac929a8b748150ef1683af89a933b76 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/stripe-chargeback-protection.md @@ -0,0 +1,18 @@ +# Stripe chargeback protection + +{% hint style="danger" %} +As soon as you suspect fraudulent activity, it is HIGHLY recommended that you enable this feature. It is more than worth the cost. +{% endhint %} + +{% hint style="warning" %} +Chargeback protection costs 0.4% extra on top of normal stripe fees on all transactions. More info here: [https://stripe.com/radar/chargeback-protection](https://stripe.com/radar/chargeback-protection) + +Also note that not all accounts are eligible to have this feature, so if you are lucky, do turn it on. +{% endhint %} + +1. Go here: [https://dashboard.stripe.com/settings/checkout](https://dashboard.stripe.com/settings/checkout) +2. Scroll to the bottom, and click turn on (in the screenshot it is already enabled + +
+ +3\. Now you are protected against any chargebacks that are marked as "fraudulent" diff --git a/TL--documentation-new/errors-and-faq/stripe-radar.md b/TL--documentation-new/errors-and-faq/stripe-radar.md new file mode 100644 index 0000000000000000000000000000000000000000..4235c7d5c2f0e2c4b10377a8d48ad543bb4c3bee --- /dev/null +++ b/TL--documentation-new/errors-and-faq/stripe-radar.md @@ -0,0 +1,65 @@ +# Stripe Radar + +{% hint style="danger" %} +Simply turning on stripe radar is NOT sufficient. You need to configure stripe radar rules. +{% endhint %} + +{% hint style="info" %} +Stripe Radar is a fraud detection and prevention system offered by Stripe. This system uses machine learning algorithms to analyze and identify patterns of fraudulent behavior, as well as to identify potential risks and suspicious transactions in real-time. By using advanced data analytics and pattern recognition techniques, Stripe Radar helps businesses prevent fraud and protect themselves from financial losses, chargebacks, and reputational damage. Stripe Radar also provides a range of customizable features, such as manual review of flagged transactions and rule-based filters, to help businesses tailor their fraud detection strategies to their specific needs. Overall, Stripe Radar is a powerful tool for businesses that want to ensure the security and integrity of their online payments and transactions. +{% endhint %} + +## Enabling stripe radar + +1. Turn on stripe radar:[ ](https://dashboard.stripe.com/settings/radar)[https://dashboard.stripe.com/settings/radar](https://dashboard.stripe.com/settings/radar) +2. Choose, turn on Stripe radar for fraud teams + +## Stripe Radar rules + +{% hint style="warning" %} +There are two types of main rules you can enable: Block rules & 3DS rules + +Block rules - These will block payments if it matches given criteria + +3DS rules- These will request 3DS verification from the customer if it matches given criteria +{% endhint %} + +{% hint style="info" %} +We will also categorize how effective each rule is at preventing fraud such as stolen credit cards. + +:red\_circle: - Very effective + +:yellow\_circle: - Effective + +:green\_circle: - Not very effective +{% endhint %} + +{% hint style="danger" %} +**We also reccomend you enabling ALL the rules listed below** +{% endhint %} + +### 3DS Rules + +
+ +The first 3 rules are already created in your stripe account, you simply need to click **enable** to activate them. + +1. :green\_circle: The first one, requests 3DS if it is required by the card +2. :yellow\_circle: The second one, requests 3DS if it is recommended by the card +3. :red\_circle: The third one, requests 3DS if it is supported by the card - This rule will make the card holder provide 3DS in almost all cases +4. :red\_circle: Last one is requesting 3DS if the user is using a VPN + + + +### Block Rules + +
+ +1. Block if Stripe thinks the customer is a high-risk customer. +2. Block if the customer is in your block list. +3. Block if the issuing country of the card is different from the customer's current IP address. +4. Block if the customer has more than 1 failed transaction. +5. Block if the CVC code entered at checkout is wrong. +6. Block if the Zip/postal code entered at checkout does not match the card billing Zip/postal code. +7. Block if the address line 1 entered at checkout does not match the cards address line 1 +8. Similar to rule 6 + diff --git a/TL--documentation-new/errors-and-faq/what-can-be-done-if-the-stripe-account-gets-suspended.md b/TL--documentation-new/errors-and-faq/what-can-be-done-if-the-stripe-account-gets-suspended.md new file mode 100644 index 0000000000000000000000000000000000000000..7fb67d584ce447f24129a9158b56ba2ad7dd6546 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/what-can-be-done-if-the-stripe-account-gets-suspended.md @@ -0,0 +1,5 @@ +# โ” What can be done if the Stripe account gets suspended? + +You have few options here. + +You can get a new account or try to get back your old account. What most people do is create a new stripe account and give it to us (TL) so that we can update the dashboard and in the mean time you can appeal the decision from stripe by saying you got scammed by fraudulent charge backs. This way you have 0 downtime in your business and you can continue selling until you get the main one back. Once you get it back we can switch it again. Further try to contact a manager on their support team and explain the situation with the fraud. diff --git a/TL--documentation-new/errors-and-faq/what-happens-if-someone-overuses-the-data.md b/TL--documentation-new/errors-and-faq/what-happens-if-someone-overuses-the-data.md new file mode 100644 index 0000000000000000000000000000000000000000..97bfa309f895c53d360b571673a2d1db99e9be23 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/what-happens-if-someone-overuses-the-data.md @@ -0,0 +1,15 @@ +# โ” What happens if someone overuses the data ? + +This is actually normal. Sometimes customers can use extra data if they have their tasks running. However, you won't be charged for the extra data. We will cover all that. + +Additionally, the next time when the customers purchase, their balance will be 0 so they won't get penalized for the extra usage. + +
+ +
+ + + +
+ +
diff --git a/TL--documentation-new/errors-and-faq/what-information-does-stripe-need-to-create-an-account.md b/TL--documentation-new/errors-and-faq/what-information-does-stripe-need-to-create-an-account.md new file mode 100644 index 0000000000000000000000000000000000000000..5de936c30fe6ef754c24da9efbca1f79c3a768ee --- /dev/null +++ b/TL--documentation-new/errors-and-faq/what-information-does-stripe-need-to-create-an-account.md @@ -0,0 +1,5 @@ +# โ” What information does Stripe need to create an account? + +Depending on what account to choose either personal or business, you will have to enter relevant information that they ask such as address, social security number and business tax ID. + +\ diff --git a/TL--documentation-new/errors-and-faq/what-is-proxy-cname.md b/TL--documentation-new/errors-and-faq/what-is-proxy-cname.md new file mode 100644 index 0000000000000000000000000000000000000000..0a2abdb870e2cab9c9e00bcabbbd3c974cf47da1 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/what-is-proxy-cname.md @@ -0,0 +1,5 @@ +# โ” What is proxy Cname ? + +Proxy Cname is a way of ask masking your proxies by redirecting your domain to the proxies. This way when the customer generates the proxies they will see your domain instead of the proxy company's name. Below is the guide on how to white label your proxies using the Cname masking method. + +[https://docs.torchlabs.xyz/onboarding-guide/white-labeling-proxies-with-your-domain](https://docs.torchlabs.xyz/onboarding-guide/white-labeling-proxies-with-your-domain) diff --git a/TL--documentation-new/errors-and-faq/what-is-the-ideal-size-of-the-logo.md b/TL--documentation-new/errors-and-faq/what-is-the-ideal-size-of-the-logo.md new file mode 100644 index 0000000000000000000000000000000000000000..2cc820a3f752338f44d454fb3d8d80adb04b5c9e --- /dev/null +++ b/TL--documentation-new/errors-and-faq/what-is-the-ideal-size-of-the-logo.md @@ -0,0 +1,3 @@ +# โ” What is the ideal size of the logo ? + +This range is good - 1332โ€Šร—โ€Š495 diff --git a/TL--documentation-new/errors-and-faq/what-needs-to-be-done-if-the-proxies-are-down-failing-not-working.md b/TL--documentation-new/errors-and-faq/what-needs-to-be-done-if-the-proxies-are-down-failing-not-working.md new file mode 100644 index 0000000000000000000000000000000000000000..3270d1725fe3c7b5beacbe4139105d4809734118 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/what-needs-to-be-done-if-the-proxies-are-down-failing-not-working.md @@ -0,0 +1,11 @@ +# โ” What needs to be done if the proxies are down / failing / not working ? + +There are few things you can do such as checking your data balance and connection. If it is still not working please send us following details. + +01\. Send us some proxies + +02\. What website you checked and what countries they are generated from + +03\. Screen Shot of the data balance + +04\. Discord tag and ID of the failed user diff --git a/TL--documentation-new/errors-and-faq/why-does-the-auto-join-feature-on-admin-dashboard-not-work.md b/TL--documentation-new/errors-and-faq/why-does-the-auto-join-feature-on-admin-dashboard-not-work.md new file mode 100644 index 0000000000000000000000000000000000000000..bf43f4c83688388df0db8fa6e537776002b914c1 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/why-does-the-auto-join-feature-on-admin-dashboard-not-work.md @@ -0,0 +1,16 @@ +# โ” Why does the auto join feature on admin dashboard not work? + +1\. Please refer to the following guide and follow the instructions. + +[https://docs.torchlabs.xyz/more-settings/enable-discord-auto-join](https://docs.torchlabs.xyz/more-settings/enable-discord-auto-join) + +2\. Make sure to check whether the permission is ticked correctly on discord developer site. [https://discord.com/developers](https://discord.com/developers) + +3\. If it doesn't work still, ask the customer to reset the token and add it on discord developer site. + +4\. Please provide following information to check whether they are matching with the database information. + +* bot\_token: +* client\_id: +* client\_secret: +* guild\_id: diff --git a/TL--documentation-new/errors-and-faq/why-has-the-datacenter-accounts-batch-oversold.md b/TL--documentation-new/errors-and-faq/why-has-the-datacenter-accounts-batch-oversold.md new file mode 100644 index 0000000000000000000000000000000000000000..d90ba538e1d8e0fbefbe47004079f5b7b8f2f7a1 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/why-has-the-datacenter-accounts-batch-oversold.md @@ -0,0 +1,3 @@ +# โ” Why has the datacenter/accounts batch oversold ? + +This happens when there is a lot of demand. When a lot of customers try to check out at the same time. We will have an update to resolve this in a couple of days. diff --git a/TL--documentation-new/errors-and-faq/why-is-the-customer-isp-plan-says-can-not-checkout.md b/TL--documentation-new/errors-and-faq/why-is-the-customer-isp-plan-says-can-not-checkout.md new file mode 100644 index 0000000000000000000000000000000000000000..c379222cd3de448a64046fa025a2ab9ae32fb95b --- /dev/null +++ b/TL--documentation-new/errors-and-faq/why-is-the-customer-isp-plan-says-can-not-checkout.md @@ -0,0 +1,5 @@ +# โ” Why is the customer ISP plan says can not checkout ? + +The tax rates need to be enabled for the prices to allow the customers to checkout for the ISP plans. + +
diff --git a/TL--documentation-new/errors-and-faq/why-is-the-data-usage-inequal-for-the-same-amount-of-tasks-from-different-providers.md b/TL--documentation-new/errors-and-faq/why-is-the-data-usage-inequal-for-the-same-amount-of-tasks-from-different-providers.md new file mode 100644 index 0000000000000000000000000000000000000000..2052e9c64f60c8de8086029ae22c2ae853c0aa00 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/why-is-the-data-usage-inequal-for-the-same-amount-of-tasks-from-different-providers.md @@ -0,0 +1,4 @@ +# โ” Why is the data usage inequal for the same amount of tasks from different providers ? + +* Could be a variety of reason such as the actual request etc. are different on each request a bot will send etc. The way Oxylabs and other providers work is that we don't have access to the proxies directly and we don't have anything in the middle as the usage is directly from Oxylabs API not from our API. The data on your account for example, every time you go to the dash and click view usage it calls Oxylabs API directly and displays the data usage. +* It's like for example when you test like 10 proxies once and you test the same proxies right after that the speed of the same proxies will be different. diff --git a/TL--documentation-new/errors-and-faq/why-is-the-data-usage-not-the-same-for-the-same-amount-of-tasks-from-different-providers.md b/TL--documentation-new/errors-and-faq/why-is-the-data-usage-not-the-same-for-the-same-amount-of-tasks-from-different-providers.md new file mode 100644 index 0000000000000000000000000000000000000000..eda91334c125ff48dfbc1ee6d5e460e50399171f --- /dev/null +++ b/TL--documentation-new/errors-and-faq/why-is-the-data-usage-not-the-same-for-the-same-amount-of-tasks-from-different-providers.md @@ -0,0 +1,5 @@ +# โ” Why is the data usage not the same for the same amount of tasks from different providers ? + +Could be a variety of reason such as the actually request etc. are different on each request a bot will send etc. The way Oxylabs works is that we don't have access to the proxies directly and we don't have anything in the middle as the usage is directly from Oxylabs API not from our API. The data on your account for example, every time you go to the dash and click view usage it calls Oxylabs API directly and displays the data usage. + +It's like for example when you test like 10 proxies once and you test the same proxies right after that the speed of the same proxies will be different. diff --git a/TL--documentation-new/errors-and-faq/why-is-the-logo-not-getting-updated-and-viewed-on-customer-dashboard.md b/TL--documentation-new/errors-and-faq/why-is-the-logo-not-getting-updated-and-viewed-on-customer-dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..89b41f2bf447f56d257ded75c4b9bac7ba77b301 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/why-is-the-logo-not-getting-updated-and-viewed-on-customer-dashboard.md @@ -0,0 +1,7 @@ +# โ” Why is the logo not getting updated and viewed on customer dashboard ? + +Browser cache has to be cleared so that the updated logo to be appeared. + +Anyone can clear their cache using this following guide: + +[https://support.google.com/accounts/answer/32050?hl=en\&co=GENIE.Platform%3DAndroid](https://support.google.com/accounts/answer/32050?hl=en\&co=GENIE.Platform%3DAndroid) diff --git a/TL--documentation-new/errors-and-faq/why-is-the-required-region-not-indicating-on-the-proxies-generated-by-some-providers.md b/TL--documentation-new/errors-and-faq/why-is-the-required-region-not-indicating-on-the-proxies-generated-by-some-providers.md new file mode 100644 index 0000000000000000000000000000000000000000..c9c22607c2115360ce6130710b6e7380b0e9586e --- /dev/null +++ b/TL--documentation-new/errors-and-faq/why-is-the-required-region-not-indicating-on-the-proxies-generated-by-some-providers.md @@ -0,0 +1,9 @@ +# โ” Why is the required region not indicating on the proxies generated by some providers ? + +The way it works is that there is a main server that accepts the requests coming to the proxies first. This server then routes the traffic to the proxies in the correct region. Like most people who have a plan with bright, they set up their servers in the US to accept the initial traffic. Some bots/proxy testers will show that the proxies are pinning in the US no matter what region they generate because they are just pining the proxies and not actually creating a request using the proxies. In reality the actually proxy is going to be the correct region. So it will still work during geo locking and all during drops. + +Anyway the proxies actually work regardless of what any tester says the region is. + +To test accurately to see which country the proxy is pinging from, please login to chrome using the proxy by following this guide: [![](https://oxylabs.io/favicon.ico)How to Use Chrome Browser Proxy Settings](https://oxylabs.io/blog/how-to-set-up-a-chrome-proxy) + +Next, please visit this link to verify what country your proxy is from: [https://lumtest.com/myip.json](https://lumtest.com/myip.json) diff --git a/TL--documentation-new/errors-and-faq/will-the-isp-product-be-removed-from-the-dashboard-after-30-days.md b/TL--documentation-new/errors-and-faq/will-the-isp-product-be-removed-from-the-dashboard-after-30-days.md new file mode 100644 index 0000000000000000000000000000000000000000..80ece893651be9161e756fe19620eee886898600 --- /dev/null +++ b/TL--documentation-new/errors-and-faq/will-the-isp-product-be-removed-from-the-dashboard-after-30-days.md @@ -0,0 +1,9 @@ +# โ” Will the ISP product be removed from the dashboard after 30 days ? + +The order will be still on their dashboard as it provides proof of delivery. What most people do is that they specify in the product description that these expire 30 days from day of purchase. The order it self has the delivery date so customers are usually pretty aware of when the proxies will expire + +If you also want to specify further when the proxies will expire for example 7 days 30 days you can use the expiration feature and link our docs page to that feature. + +[https://docs.torchlabs.xyz/data-center-and-accounts/isp-expiration-date](https://docs.torchlabs.xyz/data-center-and-accounts/isp-expiration-date) + +By enabling this and giving the proper dates you can specify when the ISPs expire. diff --git a/TL--documentation-new/general-settings/configuring-sales-analytics.md b/TL--documentation-new/general-settings/configuring-sales-analytics.md new file mode 100644 index 0000000000000000000000000000000000000000..a2079e4c0c91d2a180cc1f3db149c10790b992fa --- /dev/null +++ b/TL--documentation-new/general-settings/configuring-sales-analytics.md @@ -0,0 +1,33 @@ +# ๐Ÿ“Š Configuring sales analytics + +{% hint style="info" %} +This section will allow you to set the cost of your products in order to calculate the correct analytics data for your dashboard. + +Further this section will allow you to identify the profit , revenue , quantity and users related to Residential , datacenter and account sections separately. +{% endhint %} + +1. Go to dashboard Home page track analytics. + +![](<../.gitbook/assets/1 (62) (4).png>) + +2\. To filter analytics go to more settings and scroll below. + +![](<../.gitbook/assets/1 (63) (5).png>) + +3\. Enter the data required. + +![](<../.gitbook/assets/1 (64) (7).png>) + +4\. Then save the data entered. + +![](<../.gitbook/assets/1 (65) (2).png>) + +5\. The data entered will be converted into analytics and pop in your home page. + +![](<../.gitbook/assets/1 (66) (1).png>) + +6\. Finally you can filter the analytics as you want with data and other features. This can be done only for Residential and Datacenter products. Based on the product you can generate the analytics accordingly. + +

Residential Products

+ +

Datacenter Products

diff --git a/TL--documentation-new/general-settings/exporting-user-information.md b/TL--documentation-new/general-settings/exporting-user-information.md new file mode 100644 index 0000000000000000000000000000000000000000..c6c22dd1a4851c6df50454ba55f3f450225914b4 --- /dev/null +++ b/TL--documentation-new/general-settings/exporting-user-information.md @@ -0,0 +1,13 @@ +# โณ Exporting user information + +{% hint style="info" %} +This guide will help export the information such as discord ID, discord tag, discord avatar, email address and the created date of all the users of admin dashboard. +{% endhint %} + +{% hint style="danger" %} +Please note that Torch Labs does not take any responsibility for handling of user data. Please make sure your customers are aware of your data privacy policies. The responsibility for the user information lies solely in the hands of the user of this feature. +{% endhint %} + +โ€‹1. Go to admin dashboard and _**Users**_ tab. Then click the download icon on right corner + +
diff --git a/TL--documentation-new/general-settings/exporting-user-transactions.md b/TL--documentation-new/general-settings/exporting-user-transactions.md new file mode 100644 index 0000000000000000000000000000000000000000..9381c47e17ecde25dd0bf30e00c9e33a0b8bc0bd --- /dev/null +++ b/TL--documentation-new/general-settings/exporting-user-transactions.md @@ -0,0 +1,9 @@ +# โฌ Exporting user transactions + +{% hint style="info" %} +This guide will help to export user transactions list including the information such as transaction ID, email, discord ID, discord tag, data GB, price paid, product type, status and date. +{% endhint %} + +โ€‹1. Go to admin dashboard and _**Transactions**_ tab. Then click the download icon on right corner. + +
diff --git a/TL--documentation-new/general-settings/transaction-status.md b/TL--documentation-new/general-settings/transaction-status.md new file mode 100644 index 0000000000000000000000000000000000000000..643406de6804a89e7b431c90385241592fab5b17 --- /dev/null +++ b/TL--documentation-new/general-settings/transaction-status.md @@ -0,0 +1,35 @@ +# ๐Ÿงช Transaction status + +{% hint style="info" %} +Our transaction section has 4 main types of transactions. This page will discuss what each of the statuses mean +{% endhint %} + +### Transaction Types + +| Transaction Type | Description | +| --------------------- | ------------------------------------------------------------------------------------------- | +| Customer Order | This transaction has been created due to a customer purchasing a product. | +| Data Update | This transaction has been created due to an admin updating a user's data balance | +| Customer Subscription | This transaction has been created due to a customer purchasing a subscription type product. | + +### Status Types + +{% hint style="warning" %} +99% of the time you see the **Incomplete** status is due to the upstream provider's API giving our system a bad response. This means that their API is currently not responding to our request. +{% endhint %} + +| Status | Description | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------ | +| Complete | The order has been delivered and complete | +| Incomplete | The order has not been delivered and is not complete | +| Failed | We tried to bill the customer for a subscription, however, the charge has failed due to a lack of funds on the customer's card | +| Subscription Canceled | The customer has canceled their subscription | + +### Full Order Status + +| Transaction Type | Status | Description | +| ---------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------- | +| Customer Order | Complete | This transaction has been created due to a customer purchasing a product and the order has been delivered and complete | +| Customer Order | Incomplete | This transaction has been created due to a customer purchasing a product but the order has not been delivered and is not complete | +| Data Update | Complete | This transaction has been created due to an admin updating a user's data balance and the update has been executed and complete | +| Data Update | Incomplete | This transaction has been created due to an admin updating a user's data balance but the update has failed to execute. | diff --git a/TL--documentation-new/general-settings/transactions/README.md b/TL--documentation-new/general-settings/transactions/README.md new file mode 100644 index 0000000000000000000000000000000000000000..c886f3a60f1004eadcfd1b19d210decbd19758e0 --- /dev/null +++ b/TL--documentation-new/general-settings/transactions/README.md @@ -0,0 +1,68 @@ +# ๐Ÿ’ธ Transactions + +{% hint style="info" %} +The history of transactions can be tracked here. +{% endhint %} + +{% hint style="info" %} +Now we have divided the transactions into 02 sections such as one time (Payments) and recurring (subscription). + +Please refer to following tab for more details. + +[subscription.md](subscription.md "mention") +{% endhint %} + +1. Now transactions can be searched using an email. + +![](<../../.gitbook/assets/1 (48) (2).png>) + +2\. Every transaction has a unique ID which is called a Transaction ID. + +![](<../../.gitbook/assets/1 (49) (2).png>) + +3\. Transaction account email address can be seen here. + +![](<../../.gitbook/assets/1 (50).png>) + +4\. Discord ID and Discord tag of a transaction can be found here + +![](<../../.gitbook/assets/1 (52) (2).png>) + +5\. The GB/ DATA purchased can be seen here + +![](<../../.gitbook/assets/1 (53) (2).png>) + +6\. Price per gb/ data purchased will be here. + +![](<../../.gitbook/assets/1 (54).png>) + +7\. The purchased product will be here + +![](<../../.gitbook/assets/1 (56).png>) + +8\. The transaction type and status of the transaction can be seen here. Orders can have two main es: Completed and Incomplete. + +{% content-ref url="../transaction-status.md" %} +[transaction-status.md](../transaction-status.md) +{% endcontent-ref %} + +{% hint style="warning" %} +An order is incomplete if payment is received but the data has not been received by the user. This sometimes happens due to the upstream provider's API failing. In this case, we recommend you to go to the USERS tab and manually add data to their account. +{% endhint %} + +![](<../../.gitbook/assets/1 (57) (1).png>) + +9\. The data of the transaction placed will be here + +![](<../../.gitbook/assets/1 (59) (2).png>) + +10\. The transaction can be filtered by the status and the date . + +{% hint style="success" %} +We always recommend keeping the status set to ALL +{% endhint %} + +![](<../../.gitbook/assets/1 (61) (1).png>) + + + diff --git a/TL--documentation-new/general-settings/transactions/subscription.md b/TL--documentation-new/general-settings/transactions/subscription.md new file mode 100644 index 0000000000000000000000000000000000000000..d5c0752b908dd9833eac3962d3970af068a48ec5 --- /dev/null +++ b/TL--documentation-new/general-settings/transactions/subscription.md @@ -0,0 +1,20 @@ +# โธ Subscription + +{% hint style="info" %} +This section will provide you information regarding the subscription tab. The subscription tab includes all the recurring products and it shows the other details regarding the same products +{% endhint %} + +1. Go to admin dashboard and click on the transactions, And then click on Subscriptions + +
+ +2\. Subscription transactions can be filtered using the statuses and transactions types + +{% content-ref url="../transaction-status.md" %} +[transaction-status.md](../transaction-status.md) +{% endcontent-ref %} + +{% content-ref url="../../more-settings/searching-transactions.md" %} +[searching-transactions.md](../../more-settings/searching-transactions.md) +{% endcontent-ref %} + diff --git a/TL--documentation-new/more-settings/adding-and-removing-isp-api.md b/TL--documentation-new/more-settings/adding-and-removing-isp-api.md new file mode 100644 index 0000000000000000000000000000000000000000..25cf33447c9c812b52783be47d01e0c43e789688 --- /dev/null +++ b/TL--documentation-new/more-settings/adding-and-removing-isp-api.md @@ -0,0 +1,41 @@ +# โœ‚ Adding and Removing ISP API + +{% hint style="info" %} +This section will guide you on how to set up ISP API. When registering API, the Custom API is the one used for Tanmays Script while Porter Proxies is for the one given by porter proxies +{% endhint %} + +1. Go to _Other Settings_ tab on Admin Dashboard + +
+ +2\. Scroll down the page and click on _Register API_ + +
+ +3\. Fill the details such as Name , API end point , API Key. Then select API type. Then click on Register + +{% hint style="success" %} +we currently only support API access from Tanmay and Porter Proxies. More integrations will be added later +{% endhint %} + +{% hint style="info" %} +Make sure to use only _http_ and not to use any _/_ symbol at the end of the API end point. +{% endhint %} + +
+ +Once the API is registered you should be able to view them in the same location. Further you can create any number of APIs here. + +
+ +{% hint style="info" %} +If you want to remove an ISP API batch , click on the delete icon in front of the created ISP API batch in Other settings tab. +{% endhint %} + +
+ +{% hint style="info" %} +Customers can see now available proxies in registered API section. +{% endhint %} + +
diff --git a/TL--documentation-new/more-settings/dashboard-ui/README.md b/TL--documentation-new/more-settings/dashboard-ui/README.md new file mode 100644 index 0000000000000000000000000000000000000000..f2806e55d57d19fd99a934504d0002e3c8425cae --- /dev/null +++ b/TL--documentation-new/more-settings/dashboard-ui/README.md @@ -0,0 +1,25 @@ +# ๐ŸŽญ Dashboard UI + +{% content-ref url="uploading-primary-logo.md" %} +[uploading-primary-logo.md](uploading-primary-logo.md) +{% endcontent-ref %} + +{% content-ref url="uploading-secondary-logo.md" %} +[uploading-secondary-logo.md](uploading-secondary-logo.md) +{% endcontent-ref %} + +{% content-ref url="updating-company-name.md" %} +[updating-company-name.md](updating-company-name.md) +{% endcontent-ref %} + +{% content-ref url="updating-twitter-link.md" %} +[updating-twitter-link.md](updating-twitter-link.md) +{% endcontent-ref %} + +{% content-ref url="updating-discord-link.md" %} +[updating-discord-link.md](updating-discord-link.md) +{% endcontent-ref %} + +{% content-ref url="updating-theme.md" %} +[updating-theme.md](updating-theme.md) +{% endcontent-ref %} diff --git a/TL--documentation-new/more-settings/dashboard-ui/updating-company-name.md b/TL--documentation-new/more-settings/dashboard-ui/updating-company-name.md new file mode 100644 index 0000000000000000000000000000000000000000..8662e57131c7b9e9b927826bb70fc0cbe26be754 --- /dev/null +++ b/TL--documentation-new/more-settings/dashboard-ui/updating-company-name.md @@ -0,0 +1,23 @@ +# ๐Ÿ“› Updating Company Name + +{% hint style="info" %} +This section will guide you to update your company name to be appeared as title and footer name. +{% endhint %} + +1. Go to Admin Dashboard and click on More Settings + +
+ +2\. Enter the company name under Dashboard UI section **** and click Update. + +
+ +_The name will be updated in 02 places such as Title name and footer name._ + +**Title Name** + +
+ +**Footer Name** + +
diff --git a/TL--documentation-new/more-settings/dashboard-ui/updating-discord-link.md b/TL--documentation-new/more-settings/dashboard-ui/updating-discord-link.md new file mode 100644 index 0000000000000000000000000000000000000000..18361f7d616c46e899a4d901ea7554694e7da280 --- /dev/null +++ b/TL--documentation-new/more-settings/dashboard-ui/updating-discord-link.md @@ -0,0 +1,19 @@ +# ๐Ÿ’ฟ Updating Discord Link + +{% hint style="info" %} +This section will guide you to update your Discord Link to be appeared on the user dashboard. +{% endhint %} + +1. Go to Admin Dashboard and click on More Settings + +
+ +2\. Enter the Discord Link under Dashboard UI section **** and click Update. + +
+ + + +_The Discord will be appeared on the user dashboard as follows_ + +
diff --git a/TL--documentation-new/more-settings/dashboard-ui/updating-theme.md b/TL--documentation-new/more-settings/dashboard-ui/updating-theme.md new file mode 100644 index 0000000000000000000000000000000000000000..3c480285c2ba67ee7b480038e8bbb87c218abfba --- /dev/null +++ b/TL--documentation-new/more-settings/dashboard-ui/updating-theme.md @@ -0,0 +1,17 @@ +# ๐ŸŒ Updating Theme + +{% hint style="info" %} +This section will guide you to update your Theme to be appeared on the user dashboard. +{% endhint %} + +Referring to the following guide you can create a theme. + +{% embed url="https://docs.torchlabs.xyz/onboarding-guide/customize-dashboard-theme" %} + +1. Go to Admin Dashboard and click on More Settings + +
+ +2\. Enter the Theme under Dashboard UI section **** and click Update. + +
diff --git a/TL--documentation-new/more-settings/dashboard-ui/updating-twitter-link.md b/TL--documentation-new/more-settings/dashboard-ui/updating-twitter-link.md new file mode 100644 index 0000000000000000000000000000000000000000..75ba35fb96486504c40466fc3d8ede85b2b351b9 --- /dev/null +++ b/TL--documentation-new/more-settings/dashboard-ui/updating-twitter-link.md @@ -0,0 +1,19 @@ +# ๐ŸŒ€ Updating Twitter Link + +{% hint style="info" %} +This section will guide you to update your Twitter Link to be appeared on the user dashboard. +{% endhint %} + +1. Go to Admin Dashboard and click on More Settings + +
+ +2\. Enter the Twitter Link under Dashboard UI section **** and click Update. + +
+ + + +_The Twitter will be appeared on the user dashboard as follows_ + +
diff --git a/TL--documentation-new/more-settings/dashboard-ui/uploading-primary-logo.md b/TL--documentation-new/more-settings/dashboard-ui/uploading-primary-logo.md new file mode 100644 index 0000000000000000000000000000000000000000..c5c0581d7a902d2d1bbd04e486fdd43cc46b411b --- /dev/null +++ b/TL--documentation-new/more-settings/dashboard-ui/uploading-primary-logo.md @@ -0,0 +1,22 @@ +# ๐Ÿ” Uploading Primary Logo + +{% hint style="info" %} +This section will guide you on how to upload the primary logo. __ The primary logo is the logo which would appear on your user dashboard - left side corner. +{% endhint %} + +1. Go to Admin Dashboard and click on More Settings + +
+ +2\. Click on _Choose file_ under Dashboard UI section __ and upload your primary logo + +
+ + + +_The logo will be appeared as follows (i.e. Google)_ + +
+ + + diff --git a/TL--documentation-new/more-settings/dashboard-ui/uploading-secondary-logo.md b/TL--documentation-new/more-settings/dashboard-ui/uploading-secondary-logo.md new file mode 100644 index 0000000000000000000000000000000000000000..34d206109fa9573f9a95c00ea8dac5bb2113627e --- /dev/null +++ b/TL--documentation-new/more-settings/dashboard-ui/uploading-secondary-logo.md @@ -0,0 +1,22 @@ +# โžฐ Uploading Secondary Logo + +{% hint style="info" %} +This section will guide you on how to upload a secondary logo. __ The secondary logo is the simplified version of the primary logo that would be appearing on the tab when you open the website by using a search engine. +{% endhint %} + +1. Go to Admin Dashboard and click on More Settings + +
+ +2\. Click on _Choose file_ under Dashboard UI section __ and upload your secondary logo + +
+ +_The logo will be appeared as follows (i.e. Google)_ + +
+ +__ + + + diff --git a/TL--documentation-new/more-settings/enable-discord-auto-join.md b/TL--documentation-new/more-settings/enable-discord-auto-join.md new file mode 100644 index 0000000000000000000000000000000000000000..031ba34830e2df1268641de531f4a45dd902ec55 --- /dev/null +++ b/TL--documentation-new/more-settings/enable-discord-auto-join.md @@ -0,0 +1,45 @@ +# ๐ŸŽŸ Enable discord auto join + +{% hint style="info" %} +This section would provide you a guide on how to enable discord auto join. If you enable this anyone visits to the website would be auto joined to the discord server as well. + +If someone is already in the server this can't be experimented. +{% endhint %} + +{% embed url="https://youtu.be/xkba8GrDp6M" %} + +1. Click on the APP you made for the Authentication during the initial onboarding. + +![](<../.gitbook/assets/1 (63) (4).png>) + +2\. Go to bot and click Add bot as shows here. + +![](<../.gitbook/assets/1 (65) (4).png>) + +3\. Then click Yes. + +![](<../.gitbook/assets/1 (66) (3).png>) + +4\. Give the Bot Administrator permission. + +![](<../.gitbook/assets/1 (67) (2).png>) + +5\. Click reset token. + +![](<../.gitbook/assets/1 (68) (4).png>) + +6\. Then click yes. + +![](<../.gitbook/assets/1 (70).png>) + +7\. Next copy the token. + +![](<../.gitbook/assets/1 (72) (3).png>) + +8\. Then go to the admin dashboard and more settings, also click enable auto join. + +![](<../.gitbook/assets/1 (73) (1).png>) + +9\. Paste the token that was copied and save it. + +![](<../.gitbook/assets/1 (74) (1).png>) diff --git a/TL--documentation-new/more-settings/enabling-pagination.md b/TL--documentation-new/more-settings/enabling-pagination.md new file mode 100644 index 0000000000000000000000000000000000000000..dbed4f51c9c7aab6f1640cf01e630df519e190d9 --- /dev/null +++ b/TL--documentation-new/more-settings/enabling-pagination.md @@ -0,0 +1,15 @@ +# ๐Ÿ–‡ Enabling pagination + +{% hint style="info" %} +Products in the user dashboard will be paginated to three products per view by enabling this option. +{% endhint %} + +Normally all the products under a one category shows one after the other on the dashboard. + +![](../.gitbook/assets/Screen\_Shot\_2022-06-22\_at\_4.19.36\_PM.png) + +You can enable the option of _**enable pagination**_ to have maximum of 03 products per page as follows + +![](../.gitbook/assets/8.jpg) + +![](<../.gitbook/assets/Screen\_Shot\_2022-06-22\_at\_4.19.43\_PM (1).png>) diff --git a/TL--documentation-new/more-settings/enabling-stripe-tax.md b/TL--documentation-new/more-settings/enabling-stripe-tax.md new file mode 100644 index 0000000000000000000000000000000000000000..4ba7aabcbdcdcba57e71029f22fd14690cd03143 --- /dev/null +++ b/TL--documentation-new/more-settings/enabling-stripe-tax.md @@ -0,0 +1,25 @@ +# ๐Ÿ’ฐ Enabling Stripe Tax + +{% hint style="info" %} +This section will guide you on how to enable stripe tax. When this option is enabled, Stripe Tax allows you to calculate the tax on your customers one-time and recurring payments when customers use Checkout. +{% endhint %} + +{% hint style="info" %} +First you need to enable stripe tax on your stripe dashboard using the following instructions : [https://stripe.com/docs/tax/set-up](https://stripe.com/docs/tax/set-up) +{% endhint %} + +{% hint style="info" %} +Be cautious about the following error +{% endhint %} + +{% content-ref url="../errors-and-faq/why-is-the-customer-isp-plan-says-can-not-checkout.md" %} +[why-is-the-customer-isp-plan-says-can-not-checkout.md](../errors-and-faq/why-is-the-customer-isp-plan-says-can-not-checkout.md) +{% endcontent-ref %} + +1. Go to Admin Dashboard and click on More Settings + +
+ +2\. Enable stripe tax + +
diff --git a/TL--documentation-new/more-settings/enabling-tos-pop-up.md b/TL--documentation-new/more-settings/enabling-tos-pop-up.md new file mode 100644 index 0000000000000000000000000000000000000000..a904736b5034e853f48413d599fa5bd53b26b718 --- /dev/null +++ b/TL--documentation-new/more-settings/enabling-tos-pop-up.md @@ -0,0 +1,18 @@ +# ๐ŸŽฐ Enabling TOS pop-up + +{% hint style="success" %} +We have added a new TOS pop up option so customers are forced to accept your TOS before purchasing. This way you are protected against charge backs! +{% endhint %} + +![Example of the TOS pop up](<../.gitbook/assets/Screen Shot 2022-01-23 at 8.26.07 PM.png>) + +1. To access this, go to the _**More Settings**_ on the admin dashboard. + +![](<../.gitbook/assets/Screen Shot 2022-01-23 at 8.24.24 PM.png>) + +2\. Next, you have to enable the option by clicking on the toggle. + +![](<../.gitbook/assets/Screen Shot 2022-01-23 at 8.25.41 PM.png>) + +3\. Once enabled you must enter a link to your TOS page and click _**Save.**_ + diff --git a/TL--documentation-new/more-settings/filtering-users.md b/TL--documentation-new/more-settings/filtering-users.md new file mode 100644 index 0000000000000000000000000000000000000000..48f1f4ffdabee77434b46e0f00cbd003ad36a126 --- /dev/null +++ b/TL--documentation-new/more-settings/filtering-users.md @@ -0,0 +1,13 @@ +# ๐Ÿ˜ Filtering Users + +{% hint style="info" %} +This section will guide you to filter the users in the admin dashboard by using the filters such as discord id, discord tag and email. +{% endhint %} + +1. Go to Admin Dashboard and click on _Users_ tab + +
+ +2\. Type discord id or discord tag or email on the search bar and press enter to search a user + +
diff --git a/TL--documentation-new/more-settings/notifications-for-transactions.md b/TL--documentation-new/more-settings/notifications-for-transactions.md new file mode 100644 index 0000000000000000000000000000000000000000..aee87ec9ccb324e1657e614d27d638af28aacdf3 --- /dev/null +++ b/TL--documentation-new/more-settings/notifications-for-transactions.md @@ -0,0 +1,13 @@ +# ๐Ÿ“ฃ Notifications for transactions + +{% hint style="info" %} +The process of being updated with each transaction via email is possible, In order get that settings activated followthe below stes. +{% endhint %} + +1. From your Stripe dashboard, you can configure payment notifications to be emailed to you directly from Stripe. Just click on your avatar in the top right, then select **Profile > Email Preference** + +![](<../.gitbook/assets/Untitled design (1) (6).png>) + +2\. Scroll down and you should see a checkbox to enable emails for successful payments. + +![](<../.gitbook/assets/Untitled design (2).png>) diff --git a/TL--documentation-new/more-settings/password-page/README.md b/TL--documentation-new/more-settings/password-page/README.md new file mode 100644 index 0000000000000000000000000000000000000000..79f4de403e7edafc90fab771b7d87e6435d3b1e6 --- /dev/null +++ b/TL--documentation-new/more-settings/password-page/README.md @@ -0,0 +1,27 @@ +# ๐Ÿ”“ Password page + +{% hint style="success" %} +When using a password, everyone must enter a password. Even members with a data plan. To help these people who already have a plan, we recommend using the Limited Passwords and making them a special code. Passwords are good if you want to do a group buy and want to keep your proxies exclusive. +{% endhint %} + +If you need a more secure way to restrict the dashboard, please check : + +{% content-ref url="../restrict-dashboard-access.md" %} +[restrict-dashboard-access.md](../restrict-dashboard-access.md) +{% endcontent-ref %} + +![Example Password Page](<../../.gitbook/assets/Screen Shot 2022-01-23 at 8.10.17 PM (1).png>) + +1. You can find all the settings related to passwords in the _**Release**_ tab on the admin dashboard. + +![](<../../.gitbook/assets/Screen Shot 2022-01-23 at 8.09.22 PM.png>) + +2\. To enable the password, you must click on the toggle first. + +![](<../../.gitbook/assets/Screen Shot 2022-01-23 at 8.09.46 PM.png>) + +3\. Once the password option is enabled. To create a password, you must click the _**create password**_ button on the top right. + +![](<../../.gitbook/assets/Screen Shot 2022-01-23 at 8.09.46 PM (1).png>) + +4\. Next you will be greeted with a pop up that has two options: Limited & Non-Limited diff --git a/TL--documentation-new/more-settings/password-page/limited-password-release.md b/TL--documentation-new/more-settings/password-page/limited-password-release.md new file mode 100644 index 0000000000000000000000000000000000000000..a5a2bc9f2f5430458698843a03a8031d65190505 --- /dev/null +++ b/TL--documentation-new/more-settings/password-page/limited-password-release.md @@ -0,0 +1,15 @@ +# ๐Ÿ‘ฅ Limited password release + +{% hint style="info" %} +Limited passwords are restricted by the number of unique users. For example, you can make a password for only 10 users. Only those 10 who first used the password can use the dashboard. These 10 people can use the same password an unlimited number of times until you delete the password. +{% endhint %} + +{% hint style="success" %} +We recommend this for group buys! +{% endhint %} + +1. In the pop up, you need to enter the password and the number of valid Users. + +![](<../../.gitbook/assets/Screen Shot 2022-01-23 at 8.09.54 PM.png>) + +2\. Click _**Create Password**_ to save the password. diff --git a/TL--documentation-new/more-settings/password-page/non-limited-password-release.md b/TL--documentation-new/more-settings/password-page/non-limited-password-release.md new file mode 100644 index 0000000000000000000000000000000000000000..1573040fb729caa2a0a48d37877a36968ae2ae8b --- /dev/null +++ b/TL--documentation-new/more-settings/password-page/non-limited-password-release.md @@ -0,0 +1,11 @@ +# โฐ Non-limited password release + +{% hint style="info" %} +Non-Limited passwords are restricted by time. After a certain date the password will no longer work. However, until it is expired the password can be used by any number of people. +{% endhint %} + +1. In the pop up, you need to enter the password and the expiration date. + +![](<../../.gitbook/assets/Screen Shot 2022-01-23 at 8.10.00 PM.png>) + +2\. Click _**Create Password**_ to save the password. diff --git a/TL--documentation-new/more-settings/restrict-dashboard-access.md b/TL--documentation-new/more-settings/restrict-dashboard-access.md new file mode 100644 index 0000000000000000000000000000000000000000..21b0988b4d4ccf5c0e5f61e9f19b01c915b0231e --- /dev/null +++ b/TL--documentation-new/more-settings/restrict-dashboard-access.md @@ -0,0 +1,35 @@ +# ๐Ÿ›ก Restrict dashboard access + +{% hint style="info" %} +You can always restrict or provide access to the ones you want to give, To have more control over the dashboard follow the below steps. According to the restricted access it is a must to match the condition of been in the server and having a role both to be authorized the access. +{% endhint %} + +1. Go to the admin dashboard scroll below and click more settings and disable restricted access. + +![](<../.gitbook/assets/1 (3).jpg>) + +2\. Go to discord right-click the server and you will find the copy server. + +![](<../.gitbook/assets/2 (1).jpg>) + +> If you dont find this option to copy id please follow this link [https://www.howtogeek.com/714348/how-to-enable-or-disable-developer-mode-on-discord/](https://www.howtogeek.com/714348/how-to-enable-or-disable-developer-mode-on-discord/) + +3\. Paste it on enter guild ID and update it. + +![](<../.gitbook/assets/5 (3).jpg>) + +4\. You can also restrict the access to the dashboard by a customers role. To do this go to discord server settings, select the roles and then click the 3 dots next to the particular role to copy the ID. + +![](../.gitbook/assets/5.1.jpg) + +5\. Enter role ID and update it. + +![](../.gitbook/assets/5.2.jpg) + +6\. Finally you can test it by login to your dashboard + +![](<../.gitbook/assets/6 (1).jpg>) + +7\. You will get this popup. + +![](<../.gitbook/assets/1 (66) (5).png>) diff --git a/TL--documentation-new/more-settings/searching-transactions.md b/TL--documentation-new/more-settings/searching-transactions.md new file mode 100644 index 0000000000000000000000000000000000000000..259e15d61499ae77eeb75be917afbcb8454de7fb --- /dev/null +++ b/TL--documentation-new/more-settings/searching-transactions.md @@ -0,0 +1,34 @@ +# ๐Ÿšก Searching Transactions + +{% hint style="info" %} +This section will guide you to filter the transactions in the admin dashboard by using the filters such as discord id, discord tag, email , transaction ID, ISP, transaction type & transaction status. +{% endhint %} + +* Discord id - You can search the transactions by entering the discord ID of particular user. +* Discord tag - You can search the transactions by entering the discord tag of particular user. +* Email- You can search the transactions by entering the email ID of particular user. +* Transaction ID - You can search the transaction by entering the transaction ID of particular transaction. This would help you to identify the exact transaction with the details. +* ISP - You can search the transactions by entering the ISP and that would enable you to find to which user the ISP has been assigned to. +* Transaction type - You can filter the transactions by selecting the available transaction types such as Customer order , Data update and Customer subscription. +* Transaction status - You can filter the transactions by selecting the available transaction status such as Complete , Incomplete & Failed. + +1. Go to Admin Dashboard and click on _Transactions_ tab + +
+ +2\. Filtering Section 01 - Select the drop down arrow next to search bar and select the filter as you require (i.e. - discord id, discord tag, email , transaction ID & ISP) + +
+ +2.1. Then enter the relevant data (i.e. discord id, discord tag , email , transaction ID , ISP ) associated to the filter you selected. Then click on _search_ button. + +
+ +3\. Filtering Section 02 - Select the first drop down with _All_ on the top. Then you can filter the transactions based on the transaction type. (i.e. Customer order , Data update and customer subscription) + +
+ +4\. Filtering Section 03 - Select the second drop down with _All_ on the top. Then you can filter the transactions based on the transaction status. (i.e. Complete , Incomplete , Failed & Subscription cancelled) + +
+ diff --git a/TL--documentation-new/more-settings/sub-admin-users/README.md b/TL--documentation-new/more-settings/sub-admin-users/README.md new file mode 100644 index 0000000000000000000000000000000000000000..5f6049ccdbdc6656788fa826680014a7c4472070 --- /dev/null +++ b/TL--documentation-new/more-settings/sub-admin-users/README.md @@ -0,0 +1,52 @@ +# โ™ฃ Sub Admin Users + +{% hint style="info" %} +This section will guide you to create sub admin users by assigning different role permissions. Therefore, this function would allow delegating authority in administrating the dashboard. Furthermore, this will provide restricted access to the sub-users as you have the ability to define the roles. Also, multiple roles could be assigned to an individual role. +{% endhint %} + +{% hint style="info" %} +Please be noted that you have to share newly created credentials with new sub-users as the sub-admin users will not get any email notification regarding the assigned roles / permission. + +\ + +{% endhint %} + +### Create Role + +1. Go to Admin Dashboard, click on Sub Admin Users tab and then click on Create Role + +
+ +2\. Enter a role name and a description, Then select permission field. + +
+ +3\. Select the permission to be assigned to the particular role. Multiple permissions could be selected here. + +
+ +_Please refer the following link with the list of permissions you can assign to a role._ + +{% content-ref url="permissions.md" %} +[permissions.md](permissions.md) +{% endcontent-ref %} + +4\. Click create role and it will be indicated as Successfully created role + +
+ +5\. The created role will be appeared under the Role list. + +
+ +### Create Sub Admin User + +Once the role is created, the sub admin users could be created. + +1. Click on Create Sub Admin User + +
+ +2\. Enter the email address of the Sub Admin User to be assigned along with the password. Then select the role to assigned to the user which was created previously. Lastly click on create sub admin user. + +
diff --git a/TL--documentation-new/more-settings/sub-admin-users/permissions.md b/TL--documentation-new/more-settings/sub-admin-users/permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..0ab1956eca13b16b458ee1dc3fa8b44af0f2bc02 --- /dev/null +++ b/TL--documentation-new/more-settings/sub-admin-users/permissions.md @@ -0,0 +1,115 @@ +--- +description: >- + This guide includes all the permission roles could be assigned to a sub admin + user. +--- + +# โ›ณ Permissions + +* `all_residential` , `all_datacenter`, `all_accounts` + +These permissions allow users to view, edit, delete, and sync residential, datacenter, and accounts products. Also allows to create a batch for datacenter and accounts + +

All Products

+ +

Sync Products

+ +

Create Batches

+ +* `view_residential` , `view_datacenter`, `view_accounts` + +These permissions allow users to view only residential, datacenter, and accounts products. + +
+ +
+ +* `create_residential` , `create_datacenter`, `create_accounts` + +These permissions allow users to sync a residential, datacenter, and accounts products. and also user needs view permission for products to create. + +* `update_residential` , `update_datacenter`, `update_accounts` + +These permissions allow users to enable and disable residential, datacenter, and accounts products, create batches for datacenter and accounts and edit the description of all products. Also users need view permission for products to update. + +
+ +
+ +* `all_coupons` + +This permission allows users to view, create, and delete coupons. + +
+ +* `view_coupons` + +This permission allows users to only view coupons. + +
+ +* `create_coupons` + +This permission allows users to create coupons. also users need `view_coupons` permission to create. + +
+ +* `delete_coupons` + +This permission allows users to delete coupons. also users need `view_coupons` permission to delete. + +
+ +* `all_transactions` + +This permission allows users to view, create, update and delete transactions. + +

All Transactions

+ +

Manual Datacenter orders to fulfill

+ +* `view_transactions` + +This permission allows users to only view Transactions. + +
+ +
+ +* `update_transactions` + +This permission allows users to update Transactions and fulfill orders. also users need `view_transactions` permission to update. + +
+ +
+ +* `delete_transactions` + +This permission allows users to delete Transactions. also users need `view_transactions` permission to delete. + +
+ +* `all_users` + +This permission allows users to view and update User Dashboard Discord users. + +
+ +* `view_users` + +This permission allows users to only view User Dashboard Discord users. + +
+ +* `update_users` + +This permission allows users to Add or Subtract the Data Balance of each plan of User Dashboard Discord users. also, users need `view_users` permission to Update. + +
+ +* `view_analytics` + +This permission allows users to view Analytics. + +
diff --git a/TL--documentation-new/more-settings/transaction-discord-webhook.md b/TL--documentation-new/more-settings/transaction-discord-webhook.md new file mode 100644 index 0000000000000000000000000000000000000000..af40653058eb86f7c87b02f9385955218f08a415 --- /dev/null +++ b/TL--documentation-new/more-settings/transaction-discord-webhook.md @@ -0,0 +1,20 @@ +# ๐ŸŽž Transaction discord webhook + +{% hint style="info" %} +Enable this feature to get transactions such as purchases, renewals etc. directly recorded into your discord server. +{% endhint %} + +1. Select _**server settings**_ on discord +2. Select _**integration**_ & Click _**create webhook**_ + +![](../.gitbook/assets/5.jpg) + +3\. Then give a name and a channel to record the notification + +![](../.gitbook/assets/6.jpg) + +4\. Click _**Save Changes**_ + +5\. Click _**copy webhook URL**_ and paste on dashboard, enable _**disable webhook**_ and click _**Save.**_ + +![](../.gitbook/assets/7.jpg) diff --git a/TL--documentation-new/onboarding-guide/access-dns-settings.md b/TL--documentation-new/onboarding-guide/access-dns-settings.md new file mode 100644 index 0000000000000000000000000000000000000000..cf8e6bda60a1c121801fdf71d8450af485479bc1 --- /dev/null +++ b/TL--documentation-new/onboarding-guide/access-dns-settings.md @@ -0,0 +1,39 @@ +# ๐ŸŒ Access DNS settings + +{% hint style="info" %} +There are many reasons you might want to use a third-party DNS server, from parental controls and security features to speed and reliability improvements. You can change the DNS server for your entire home network on your router, or set it individually on a PC, Mac, iPhone, iPad, Android device, Chromebook, or many other devices. +{% endhint %} + +## Godaddy DNS settings + +1. Click on Domains and then click on _**All Domains**_ + +![](<../.gitbook/assets/image (9).png>) + +2\. From the list of your current domains, click on the domain you own. + +![](<../.gitbook/assets/image (6).png>) + +3\. Next, scroll all the way to the end of the page and you should see a _**Manage DNS**_ option + +![](<../.gitbook/assets/image (14).png>) + +4\. Here you can add your new DNS records + +![](<../.gitbook/assets/image (2).png>) + +## Namecheap DNS settings + +1. Click on your _**Account**_ and then choose _**Domain List.**_ + +![](<../.gitbook/assets/image (12).png>) + +2\. Find your domain and click _**Manage.**_ + +![](<../.gitbook/assets/image (11).png>) + +3\. Next, go to the _**Advanced DNS**_ tab. + +![](<../.gitbook/assets/image (13).png>) + +4\. Now you can create any DNS record you want diff --git a/TL--documentation-new/onboarding-guide/adding-your-site-to-your-domain.md b/TL--documentation-new/onboarding-guide/adding-your-site-to-your-domain.md new file mode 100644 index 0000000000000000000000000000000000000000..51a7bcc296e8f66d9eecb24fb3e4a49ed7279591 --- /dev/null +++ b/TL--documentation-new/onboarding-guide/adding-your-site-to-your-domain.md @@ -0,0 +1,75 @@ +# โœˆ Adding Your Site To Your Domain + +{% hint style="info" %} +If youโ€™re looking to connect your GoDaddy domain to your website you will need two things: a domain, and a hosting account. The hosting account (or server) is where your website will live. GoDaddy is where you might buy your domain and in orde to connect your domain with site follow the below steps. +{% endhint %} + +## Godaddy Setup + +1. Go to your Domain provider's DNS settings + +Godaddy:[https://www.godaddy.com/help/what-is-dns-665](https://www.godaddy.com/help/what-is-dns-665) + +2\. Create a C Name Record pointing to the domain. + +![](../.gitbook/assets/Untitled.png) + +3\. In the Name/host section add "www" what this does is we are adding www in front of your domain. So it will be [www.yourdomain.com](http://www.yourdomain.com) + +{% hint style="warning" %} +If you already have a landing page that is occupying your WWW cname, you can put your site on a different cname such as "dashboard". What this will do is your dashboard will now live on the dashboard.domain.com. If you decide to do this, **please SKIP steps 6 to 9.** +{% endhint %} + +4\. In the value/points to section, add the link we have provided you on discord. We will provide you with a link that we host on our backend which will be a randomized link. So to point your newly bought domain, you must point that domain to the link we have provided you. + +5\. TTL can be anything you want. We recommend a shorter TTL since it is basically how long it takes for the changes to go into effect. + +6\. Next, we need to create an A record in the DNS settings. + +![](<../.gitbook/assets/Untitled (1).png>) + +7\. In the Name/host section add your domain only. Do not add www or https just the domain. + +8\. In the value/points to section, add: **75.2.60.5** + +9\. TTL can be anything you want. We recommend a shorter TTL since it is basically how long it takes for the changes to go into effect. + +10\. That's it! Your site should be good to go in a couple of hours after the changes have gone into effect. ๐ŸŽ‰ + +## **NameCheap / Google Setup** + +1. Go to your Domain provider's DNS settings + +NameCheap:[https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-to-change-dns-for-a-domain/](https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-to-change-dns-for-a-domain/) + +2\. Create a C Name Record pointing to the domain. + +
+ +3\. In the Name/host section add "www" what this does is we are adding www in front of your domain. So it will be [www.yourdomain.com](http://www.yourdomain.com) + +{% hint style="warning" %} +If you already have a landing page that is occupying your WWW cname, you can put your site on a different cname such as "dashboard". What this will do is your dashboard will now live on the dashboard.domain.com. If you decide to do this, **please SKIP steps 6 to 9.** +{% endhint %} + +4\. In the value/points to section, add the link we have provided you on discord. We will provide you with a link that we host on our backend which will be a randomized link. So to point your newly bought domain, you must point that domain to the link we have provided you. + +5\. TTL can be anything you want. We recommend a shorter TTL since it is basically how long it takes for the changes to go into effect. + +6\. Next, we need to create an A record in the DNS settings. + +
+ +7\. In the Name/host section add your domain only. Do not add www or https just the domain. + +8\. In the value/points to section, add: **75.2.60.5** + +9\. TTL can be anything you want. We recommend a shorter TTL since it is basically how long it takes for the changes to go into effect. + +10\. Make the below record exactly as shown: + +Create an **ALIAS Record** + +
+ +11\. That's it! Your site should be good to go in a couple of hours after the changes have gone into effect. ๐ŸŽ‰ diff --git a/TL--documentation-new/onboarding-guide/customize-dashboard-theme.md b/TL--documentation-new/onboarding-guide/customize-dashboard-theme.md new file mode 100644 index 0000000000000000000000000000000000000000..441fbadafd248fa2559b7d104258b782ea12a5df --- /dev/null +++ b/TL--documentation-new/onboarding-guide/customize-dashboard-theme.md @@ -0,0 +1,35 @@ +# ๐Ÿ’Š Customize dashboard theme + +{% hint style="info" %} +The dashboard theme is 100% customizable, Follow the below steps to customer your dashboard theme. +{% endhint %} + +{% embed url="https://youtu.be/PbzB9H1UcVA" %} + +1. To edit the Dashboard Theme, Click the icon in the top right. + +![](<../.gitbook/assets/Untitled design.png>) + +2\. Choose the primary colour of the dashboard from the Colour Pallete. + +![](<../.gitbook/assets/Untitled design (1) (12).png>) + +3\. Then choose your Dashboard background colour. + +![](<../.gitbook/assets/Untitled design (2) (2).png>) + +4\. Set your required saturation of the Dashboard. + +![](<../.gitbook/assets/Untitled design (3) (3).png>) + +5\. Also finally set the Lightness in your Dashboard. + +![](<../.gitbook/assets/Untitled design (4) (11).png>) + +6\. Finally, Click below marked area to Copy the Theme colour of the Dashboard. + +![](<../.gitbook/assets/Untitled design (5) (1).png>) + +7\. After copying the theme, submit the theme code on the form. + +
diff --git a/TL--documentation-new/onboarding-guide/find-discord-id.md b/TL--documentation-new/onboarding-guide/find-discord-id.md new file mode 100644 index 0000000000000000000000000000000000000000..f8a485c234d7ac4a4acf77d2b878c3584b0d8bf4 --- /dev/null +++ b/TL--documentation-new/onboarding-guide/find-discord-id.md @@ -0,0 +1,31 @@ +# ๐Ÿ—ƒ Find Discord ID + +{% hint style="info" %} +Users, individual messages, and entire Discord servers all have a multi-digit ID number that can be used in various cases. While you can use Discord entirely without knowing any of these ID numbers, some circumstances may arise where you need to get one, just in case. Here are the steps to find any of those! +{% endhint %} + +{% embed url="https://youtu.be/gviB5ke2ZeQ" %} + +1. In order to find the discord tag, Please log in to Discord. + +![](<../.gitbook/assets/Untitled design (22).png>) + +2\. Select Settings from the drop-down menu on the left side of the discord. + +![](<../.gitbook/assets/Untitled design (1) (2).png>) + +3\. Then scroll down and select Advanced from the drop-down menu. + +![](<../.gitbook/assets/Untitled design (2) (8).png>) + +4\. Press above the marked area to on the Developer Mode. + +![](<../.gitbook/assets/Untitled design (3) (7).png>) + +5\. Then click above the Torch Lab Icon. + +![](<../.gitbook/assets/Untitled design (4) (9).png>) + +6\. Below the list of options find Copy ID and Paste wherever is required. + +![](<../.gitbook/assets/Untitled design (5) (4).png>) diff --git a/TL--documentation-new/onboarding-guide/onboarding-a-residential-product.md b/TL--documentation-new/onboarding-guide/onboarding-a-residential-product.md new file mode 100644 index 0000000000000000000000000000000000000000..d1b7fabefb479929732527391f45e3a33ff4feda --- /dev/null +++ b/TL--documentation-new/onboarding-guide/onboarding-a-residential-product.md @@ -0,0 +1,83 @@ +# โœ… Onboarding a residential product + +{% hint style="info" %} +This guide will help to set up residential products for your dashboard. +{% endhint %} + +{% content-ref url="../product-settings/product-metadata.md" %} +[product-metadata.md](../product-settings/product-metadata.md) +{% endcontent-ref %} + +{% embed url="https://youtu.be/ugkvgPD_kfg" %} + +1. In order to set up the Stripe Product follow the below-mentioned steps. + +![](<../.gitbook/assets/Untitled design (15).png>) + +2\. Firstly, Log in to the Stripe Account. + +![](<../.gitbook/assets/Untitled design (1) (3).png>) + +3\. Right Side of the Stripe Dashboard find Products and click that. + +![](<../.gitbook/assets/Untitled design (2) (10).png>) + +4\. Next Add Products + +![](<../.gitbook/assets/Untitled design (3) (10).png>) + +5\. Then name your product + +![](<../.gitbook/assets/Untitled design (4) (1).png>) + +6\. Also set the price for your product. + +![](<../.gitbook/assets/Untitled design (5) (6).png>) + +7\. Click "One Time" below Price. + +![](<../.gitbook/assets/Untitled design (6) (2).png>) + +8\. To add another product, Repeat the process. + +![](<../.gitbook/assets/Untitled design (7) (2).png>) + +9\. After adding the products, View Additional Options. + +![](<../.gitbook/assets/Untitled design (8) (6).png>) + +10\. Then add Metadata Key the exact text for the MetaData section can be found below, Copy and Paste from the below to omit errors. Then save the product. + +![](<../.gitbook/assets/Untitled design (2) (1).png>) + +11\. Here you can view all the prices created, And click on a price. + +![](<../.gitbook/assets/Untitled design (1) (8).png>) + + + +12\. To add bandwidth limit Click Edit MetaData. In the first field add "data\_gb" followed but your desired No. of GB for that price and save. And repeat the same for other prices as well. + +![](<../.gitbook/assets/Untitled design (11) (7).png>) + +13\. Now go-to products and now we are done with our first product. We do not recommend making more than 6 prices per product. + +![](<../.gitbook/assets/Untitled design (12) (2).png>) + +14\. Then go back to the onboarding site and choose the plan we just set up. + +![](<../.gitbook/assets/Untitled design (13) (2).png>) + +15\. And then sync with the stripe. + +![](<../.gitbook/assets/Untitled design (14) (1).png>) + +16\. If everything goes well you should see your GB next to the prices you set. + +![](<../.gitbook/assets/Untitled design (15) (4).png>) + + + +17\. Repeat this process if you are using multiple API's. + +![](<../.gitbook/assets/Untitled design (3) (4).png>) diff --git a/TL--documentation-new/onboarding-guide/setting-up-a-domain.md b/TL--documentation-new/onboarding-guide/setting-up-a-domain.md new file mode 100644 index 0000000000000000000000000000000000000000..0ba586ed3251c35aad81c967cb727fa8a34c22ed --- /dev/null +++ b/TL--documentation-new/onboarding-guide/setting-up-a-domain.md @@ -0,0 +1,11 @@ +# ๐Ÿชก Setting Up A Domain + +Buying Domain From GoDaddy + +{% embed url="https://www.youtube.com/watch?t=8s&v=z-AsgoQrnTk" %} + +Buying Domain From NameCheap + +{% embed url="https://www.youtube.com/watch?v=AgmOUicbDjo" %} + +After buying a domain, make sure to submit the domain on our onboarding website. Please make sure you enter it exactly how it appears as it is case-sensitive! diff --git a/TL--documentation-new/onboarding-guide/setting-up-a-stripe-account.md b/TL--documentation-new/onboarding-guide/setting-up-a-stripe-account.md new file mode 100644 index 0000000000000000000000000000000000000000..23285878209f2ad8cd843d7e7d9fce3ab7c7a366 --- /dev/null +++ b/TL--documentation-new/onboarding-guide/setting-up-a-stripe-account.md @@ -0,0 +1,13 @@ +# ๐Ÿ”„ Setting Up A Stripe Account + +**IMPORTANT** + +{% hint style="info" %} +:warning: Please do not put SELLING PROXIES OR ANYTHING RELATED TO PROXIES in the product description section in BUSINESS DETAILS (2:25 minutes in the video). Instead, you can put selling software or something tech-related. +{% endhint %} + +{% embed url="https://www.youtube.com/watch?v=-g3nUV_y648" %} + +#### For the business website, if you do not have a website, please use your company's Twitter link. You can update this link once you buy a domain later. + +{% embed url="https://www.youtube.com/watch?v=Heil-DNd-ug" %} diff --git a/TL--documentation-new/onboarding-guide/setting-up-discord-authentication.md b/TL--documentation-new/onboarding-guide/setting-up-discord-authentication.md new file mode 100644 index 0000000000000000000000000000000000000000..3e6867fadd2eee4eaa4cea3589be1fe9dfd8d4d1 --- /dev/null +++ b/TL--documentation-new/onboarding-guide/setting-up-discord-authentication.md @@ -0,0 +1,79 @@ +# โš™ Setting up discord authentication + +{% hint style="info" %} +Two-factor authentication, or 2FA, is a smart method to add an extra layer of protection to your Discord account by ensuring that only you can log in. +{% endhint %} + +{% embed url="https://youtu.be/4wXkn4GG20E" %} + +1. To set up discord authenticator, Follow the discord developer link mentioned here. [https://discord.com/developers](https://discord.com/developers) + +![](<../.gitbook/assets/Untitled design (9).png>) + +2\. Click the new "Application" + +![](<../.gitbook/assets/Untitled design (1) (7).png>) + +3\. Name your application - We recommend using your company name and click "Create". + +![](<../.gitbook/assets/Untitled design (3) 4.png>) + +4\. Then upload your company logo. + +![](<../.gitbook/assets/Untitled design (3).png>) + +5\. Left side of the Dashboard click the OAuth2. + +![](<../.gitbook/assets/Untitled design (6) (5).png>) + +6\. Here copy the Client ID. + +![](<../.gitbook/assets/Untitled design (5) (7).png>) + +7\. Here paste your Client ID. + +![](<../.gitbook/assets/Untitled design (6).png>) + + + +8\. Here again copy the Client Secret from discord. + +![](<../.gitbook/assets/Untitled design (4) (10).png>) + +9\. Here paste the Client Secret. + +![](<../.gitbook/assets/Untitled design (8) (2).png>) + + + +10\. Click URL from the site and paste in Discord Developer. + +![](<../.gitbook/assets/Untitled design (9) (3).png>) + + + +11\. Click Add Redirect, Paste the URL here and Click save. + +[https://auth-service-w34nvoxnwq-uc.a.run.app/api/v1/auth/discord/callback](https://auth-service-w34nvoxnwq-uc.a.run.app/api/v1/auth/discord/callback) + +![](<../.gitbook/assets/Untitled design (3) (5).png>) + +12\. Choose this option, If you want members to automatically join your server. + +![](<../.gitbook/assets/Untitled design (2) (6).png>) + +13\. Copy your Server ID from Discord. + +![](<../.gitbook/assets/Untitled design (1) (10).png>) + +14\. Click the Torch Lab Icon. + +![](<../.gitbook/assets/Untitled design (12) (5).png>) + +15\. Copy your Server ID. + +![](<../.gitbook/assets/Untitled design (13) (4).png>) + +16\. Paste the Server ID and save details. + +![](<../.gitbook/assets/Untitled design (13).png>) diff --git a/TL--documentation-new/onboarding-guide/white-labeling-proxies-with-your-domain.md b/TL--documentation-new/onboarding-guide/white-labeling-proxies-with-your-domain.md new file mode 100644 index 0000000000000000000000000000000000000000..18c2a65da657e1db4769f70ae1a3f897c360c28c --- /dev/null +++ b/TL--documentation-new/onboarding-guide/white-labeling-proxies-with-your-domain.md @@ -0,0 +1,103 @@ +# ใ€ฝ White labeling proxies with your domain + +{% hint style="info" %} +This process allows you to brand the proxies with your company name. For example, if you are using packet stream the default proxies will have [packetstream.io](http://packetstream.io) in the name. However, using the following guide you can use your domain instead to brand the proxies. +{% endhint %} + +#### Quick Domain Links + +| API | Record Type | Domain | +| ------------ | ----------- | -------------------------------------------------- | +| Smartproxies | CNAME | gate.smartproxy.com | +| Oxylabs | CNAME | pr.oxylabs.io | +| Packetstream | CNAME | proxy.packetstream.io | +| Private | A | 159.89.245.182 | +| IPRoyal | CNAME | proxy.iproyal.com | +| Brightdata | CNAME | pmgr-customer-c\_e65c4ff1.zproxy.lum-superproxy.io | + +#### PacketStream + +Use this method to brand your proxies with your own domain/company name + +To brand the proxies under your domain follow these steps: + +1. Open the DNS configuration for your domain. +2. Create a C Name Record pointing to the domain. +3. Whatever you enter in name/host will decide the domain which points to our API IP. +4. Thus if your domain is [API.com](http://api.com/) and you enter the host premium or whatever you want to call it pointing to the PacketStream domain, your proxies will be formatted [premium.yourdomain.com](http://premium.yourdomain.com/):port:user:pass +5. An example on Godaddy is linked below: + +![](../.gitbook/assets/Screen\_Shot\_2021-08-14\_at\_10.45.30\_PM.png) + +#### Private Resis + +Use this method to brand your proxies with your own domain/company name + +To brand the proxies under your domain follow these steps: + +1. Open the DNS configuration for your domain. +2. Create a A Name Record pointing to the domain {**159.89.245.182}**. +3. Whatever you enter in name/host will decide the domain which points to our API IP. +4. Thus if your domain is [API.com](http://api.com/) and you enter the host premium pointing to the oxylabs domain, your proxies will be formatted [premium.yourdomain.com](http://premium.yourdomain.com/):port:user:pass +5. An example on Godaddy is linked below: + +![](../.gitbook/assets/Screen\_Shot\_2021-08-14\_at\_10.06.51\_PM.png) + +#### Oxylabs + +Use this method to brand your proxies with your own domain/company name + +To brand the proxies under your domain follow these steps: + +1. Open the DNS configuration for your domain. +2. Create a C Name Record pointing to the domain. +3. Whatever you enter in name/host will decide the domain which points to our API IP. +4. Thus if your domain is [API.com](http://api.com/) and you enter the host premium pointing to the oxylabs domain, your proxies will be formatted [premium.yourdomain.com](http://premium.yourdomain.com/):port:user:pass +5. An example on Godaddy is linked below: + + + +![](../.gitbook/assets/Screen\_Shot\_2021-08-11\_at\_8.39.44\_PM.png) + +#### Smart Proxies + +Use this method to brand your proxies with your own domain/company name + +To brand the proxies under your domain follow these steps: + +1. Open the DNS configuration for your domain. +2. Create a C Name Record pointing to the domain. +3. Whatever you enter in name/host will decide the domain which points to our API IP. +4. Thus if your domain is [API.com](http://api.com/) and you enter the host premium pointing to the Smart Proxies domain, your proxies will be formatted [premium.yourdomain.com](http://premium.yourdomain.com/):port:user:pass +5. An example on Godaddy is linked below: + +![](<../.gitbook/assets/Screen Shot 2022-03-25 at 7.52.39 PM (1).png>) + +#### IP Royal + +Use this method to brand your proxies with your own domain/company name + +To brand the proxies under your domain follow these steps: + +1. Open the DNS configuration for your domain. +2. Create a C Name Record pointing to the domain. +3. Whatever you enter in name/host will decide the domain which points to our API IP. +4. Thus if your domain is [API.com](http://api.com/) and you enter the host premium or whatever you want to call it pointing to the PacketStream domain, your proxies will be formatted [premium.yourdomain.com](http://premium.yourdomain.com/):port:user:pass +5. An example on Godaddy is linked below: + +
+ +#### Brightdata + +Use this method to brand your proxies with your own domain/company name + +To brand the proxies under your domain follow these steps: + +1. Open the DNS configuration for your domain. +2. Create a C Name Record pointing to the domain. +3. Whatever you enter in name/host will decide the domain which points to our API IP. +4. Thus if your domain is [API.com](http://api.com/) and you enter the host premium or whatever you want to call it pointing to the PacketStream domain, your proxies will be formatted [premium.yourdomain.com](http://premium.yourdomain.com/):port:user:pass +5. An example on Godaddy is linked below: + +
+ diff --git a/TL--documentation-new/product-settings/change-price-of-a-product.md b/TL--documentation-new/product-settings/change-price-of-a-product.md new file mode 100644 index 0000000000000000000000000000000000000000..a7a6e17bec05981bdb2682da1921818019513f91 --- /dev/null +++ b/TL--documentation-new/product-settings/change-price-of-a-product.md @@ -0,0 +1,59 @@ +# ๐Ÿ’ฐ Change price of a product + +{% hint style="info" %} +This guide will be useful if the prices of any of the products are adjusted or eliminated. + + +{% endhint %} + +1. To change or remove the price of a product, this guide will be helpful. As mentioned below To change the price of the Plan Killer Basic data follow the guide. + +![](<../.gitbook/assets/Untitled design (27).png>) + +2\. Go to your Stripe account and products. + +![](<../.gitbook/assets/Untitled design (2) (3).png>) + +3\. Then go to the "Overview" page. + +![](<../.gitbook/assets/Untitled design (1) (4).png>) + +4\. Choose the correct plan as shown below "Killer Basic". + +![](<../.gitbook/assets/Untitled design (3) (1).png>) + +5\. Once choose the correct product, Then choose the correct price. + +![](<../.gitbook/assets/Untitled design (4) (4).png>) + +6\. Copy the metadata, And if you know the metadata then you don't have to copy it. + +![](<../.gitbook/assets/Untitled design (5) (5).png>) + +7\. The existing price needs to be archived before adding new, In order to do that click the three dots marked and you will get some options from that choose archive price. + +![](<../.gitbook/assets/Untitled design (7) (1).png>) + +8\. As shown then go to "Add Another Price" + +![](<../.gitbook/assets/Untitled design (6) (1).png>) + +9\. Here choose one time, Give your desired price and finally "Add Price" + +![](<../.gitbook/assets/Untitled design (8) (7).png>) + +10\. Then click above the change made price. + +![](<../.gitbook/assets/Untitled design (9) (7).png>) + +11\. Then edit Metadata and insert the value finally save metadata. + +![](<../.gitbook/assets/1 (3).png>) + +12\. Here you will see the changes made. + +![](<../.gitbook/assets/1 (1).png>) + +13\. Again back to Dashboard, Now Sync with stripe. Eventually, refresh the page again. + +![](<../.gitbook/assets/1 (2).png>) diff --git a/TL--documentation-new/product-settings/changing-product-description.md b/TL--documentation-new/product-settings/changing-product-description.md new file mode 100644 index 0000000000000000000000000000000000000000..2382a5ace980909b2011632b2286df84a410aab4 --- /dev/null +++ b/TL--documentation-new/product-settings/changing-product-description.md @@ -0,0 +1,29 @@ +# ๐Ÿ“œ Changing Product Description + +{% hint style="info" %} +In order to change or update the descriptions of your products, follow the below instructions. +{% endhint %} + +1. You can chage or update the below description. + +![](<../.gitbook/assets/1 (90).png>) + +2\. Go to Dashboard and Products + +![](<../.gitbook/assets/1 (91).png>) + +3\. Click the Edit icon here + +![](<../.gitbook/assets/1 (92).png>) + +4\. Click Dashboard Description + +![](<../.gitbook/assets/1 (94) (1).png>) + +5\. Update your description then you can see a preview of how it will be on the website and finally save it. + +{% hint style="info" %} +Our dashboard description supports markdown syntax! read the quick [cheat sheet](https://www.markdownguide.org/cheat-sheet/) to take advantage of its powerful features. +{% endhint %} + +![](<../.gitbook/assets/1 (95).png>) diff --git a/TL--documentation-new/product-settings/changing-tab-names.md b/TL--documentation-new/product-settings/changing-tab-names.md new file mode 100644 index 0000000000000000000000000000000000000000..f97b5da6561e4eeb7059476c7a349ce3b1a674c5 --- /dev/null +++ b/TL--documentation-new/product-settings/changing-tab-names.md @@ -0,0 +1,23 @@ +--- +description: >- + This guide will help you to change the names of the customer dashboard tabs by + using the admin dashboard. +--- + +# ๐Ÿ“‘ Changing tab names + +{% hint style="info" %} +This guide will help you to change the products name displayed on the User Dashboard. +{% endhint %} + +Go to more settings on admin dashboard and under product details the product names could be edited as required. + +![](<../.gitbook/assets/1 (2).jpg>) + +For an example the tab names could be renamed as Tab 1, Tab 2 and Tab 3 as needed. + +![](../.gitbook/assets/4.jpg) + +The above changes would be displayed on the customer dashboard as follows + +![](<../.gitbook/assets/5 (1).jpg>) diff --git a/TL--documentation-new/product-settings/coupons/README.md b/TL--documentation-new/product-settings/coupons/README.md new file mode 100644 index 0000000000000000000000000000000000000000..2d556c85f53dce47a33e09837febbeb2f2bceb33 --- /dev/null +++ b/TL--documentation-new/product-settings/coupons/README.md @@ -0,0 +1,44 @@ +# ๐Ÿ’ฒ Coupons + +{% hint style="info" %} +> Disclaimer - For subscription products if you create a coupon it applies to every recurring payment and not only for the initial payment. One-time coupons coming soon. +{% endhint %} + +To create coupons for clients for any promotional activities please follow this guide. + +1. This will be the Coupon Session, Where coupons can be created for customers. + +![](<../../.gitbook/assets/Untitled design (25).png>) + +2\. These are Coupon Codes, This can be copied by clicking top of that and pasting on the required place. + +![](<../../.gitbook/assets/Untitled design (1) (9).png>) + +3\. The coupons can be Limited and non Limited to usage. That will be the Type of Coupon that appeared here. + +![](<../../.gitbook/assets/Untitled design (2) (4).png>) + +4\. The expiry of the coupon will be here for Non limited type coupons and users for limited type Coupons. + +![](<../../.gitbook/assets/Untitled design (3) (12).png>) + +5\. How many times the Coupon redeemed will appear here. + +![](<../../.gitbook/assets/Untitled design (4) (8).png>) + +6\. The time and date created of this Coupon will appear here. + +![](<../../.gitbook/assets/Untitled design (5).png>) + +7\. Now the Coupon can be created by clicking here. + +![](<../../.gitbook/assets/Untitled design (6) (7).png>) + +8\. Now to create a **Limited Coupon**, Click the top of **Limited** then type your at **Coupon Name** also enter the Number of Users at **Number of Users** space. Now the discount percentage should be given at **Percent Discount** and choose your Plans from the Dropdown of **Plans**. + +![](<../../.gitbook/assets/Untitled design (7) (3).png>) + +9\. Now to create a **Non** **Limited Coupon**, Click the top of **Non** **Limited** then type your at **Coupon Name** also enter the expiry date at **Coupon Expiry** space. Now the discount percentage should be given at **Percent Discount** and choose your Plans from the Dropdown of **Plans**. + +![](<../../.gitbook/assets/Untitled design (8).png>) + diff --git a/TL--documentation-new/product-settings/coupons/limited-coupon.md b/TL--documentation-new/product-settings/coupons/limited-coupon.md new file mode 100644 index 0000000000000000000000000000000000000000..5ce9e9395e806787647f39c7de16bf58492a15ea --- /dev/null +++ b/TL--documentation-new/product-settings/coupons/limited-coupon.md @@ -0,0 +1,5 @@ +# ๐Ÿ‘ฅ Limited Coupon + +{% hint style="info" %} +Limited coupons have a limit on how many times they can be redeemed. These are not restricted by time but only my number of uses. +{% endhint %} diff --git a/TL--documentation-new/product-settings/coupons/non-limited-coupon.md b/TL--documentation-new/product-settings/coupons/non-limited-coupon.md new file mode 100644 index 0000000000000000000000000000000000000000..9006609f13e4f3a054a93f03ef2388b881ac2a7b --- /dev/null +++ b/TL--documentation-new/product-settings/coupons/non-limited-coupon.md @@ -0,0 +1,5 @@ +# โฐ Non-Limited Coupon + +{% hint style="info" %} +Non-limited coupons can be redeemed indefinitely before the given expiry date and not capped by number of uses +{% endhint %} diff --git a/TL--documentation-new/product-settings/creating-a-recurring-price-for-a-product.md b/TL--documentation-new/product-settings/creating-a-recurring-price-for-a-product.md new file mode 100644 index 0000000000000000000000000000000000000000..10f21be6a7b01b98ffbd3f76279f1ae27870bc5e --- /dev/null +++ b/TL--documentation-new/product-settings/creating-a-recurring-price-for-a-product.md @@ -0,0 +1,56 @@ +# โ™ป Creating a recurring price for a product + +{% hint style="success" %} +Any product can have two types of prices: + +1. One-time - Customer is billed once +2. Recurring - Customer is billed on a recurring basis (eg: Monthly) + + + +You can add recurring prices to any existing product. + +Each product can have both one-time and recurring prices at the same time. +{% endhint %} + +{% hint style="warning" %} +Recurring products are only available for Datacenter and Accounts products only at the moment. Residential products are coming soon. + +Only each successive billing cycle, the customer will be delivered the originally delivered product on their first checkout. They **will not** be delivered a new list each time their subscription updates. + +If you want to update their delivered product, you can do so by following the below guide: [https://docs.torchlabs.xyz/data-center-and-accounts/edit-and-view-delivered-a-products](https://docs.torchlabs.xyz/data-center-and-accounts/edit-and-view-delivered-a-products) +{% endhint %} + +**Before you add a recurring price, you also need to make sure you have the customer billing portal set up as well.** + +{% content-ref url="../customer-dashboard/customer-subscription-portal.md" %} +[customer-subscription-portal.md](../customer-dashboard/customer-subscription-portal.md) +{% endcontent-ref %} + +1. To add recurring prices, go to an existing product you have created within Stripe. + +![](<../.gitbook/assets/Screen Shot 2022-06-26 at 12.41.31 PM.png>) + +2\. Click on Add Another Price. + +![](<../.gitbook/assets/Screen Shot 2022-06-26 at 12.41.40 PM.png>) + +3\. Next, put your desired price and choose "Recurring" and click add price. + +![](<../.gitbook/assets/Screen Shot 2022-06-26 at 12.41.56 PM.png>) + +4\. Next, you need to add the meta data to specify the quantity you wish to deliver at the given price point. + +For detailed instructions refer to each product setup page and metadata can be found below + +{% content-ref url="product-metadata.md" %} +[product-metadata.md](product-metadata.md) +{% endcontent-ref %} + +![](<../.gitbook/assets/Screen Shot 2022-06-26 at 12.42.29 PM.png>) + +5\. You can now see that we have successfully created a recurring product since we have a price with /month next to it. + +![](<../.gitbook/assets/Screen Shot 2022-06-26 at 12.42.35 PM.png>) + +6\. Finally, head over the admin dashboard and sync your products following the usualy process. diff --git a/TL--documentation-new/product-settings/deleting-a-product-price.md b/TL--documentation-new/product-settings/deleting-a-product-price.md new file mode 100644 index 0000000000000000000000000000000000000000..7f194349189c9031ed6e8c5d408dacdfb46d1971 --- /dev/null +++ b/TL--documentation-new/product-settings/deleting-a-product-price.md @@ -0,0 +1,37 @@ +# โŒ Deleting a product price + +{% hint style="info" %} +This guide will be useful if any of the products' prices are to be eliminated. +{% endhint %} + +1. To remove the price of a product, this guide will be helpful. As mentioned below To remove the price of the Plan Killer Basic data follow the guide. + +![](<../.gitbook/assets/Untitled design (27).png>) + +2\. Go to your Stripe account and products. + +![](<../.gitbook/assets/Untitled design (2) (3).png>) + +3\. Then go to the "Overview" page. + +![](<../.gitbook/assets/Untitled design (1) (4).png>) + +4\. Choose the correct plan as shown below "Killer Basic". + +![](<../.gitbook/assets/Untitled design (3) (1).png>) + +5\. Once choose the correct product, Then choose the correct price. + +![](<../.gitbook/assets/Untitled design (4) (4).png>) + +6\. Copy the metadata, And if you know the metadata then you don't have to copy it. + +![](<../.gitbook/assets/Untitled design (5) (5).png>) + +7\. The existing price needs to be archived before adding new, In order to do that click the three dots marked and you will get some options from that choose archive price. + +![](<../.gitbook/assets/Untitled design (7) (1).png>) + +8\. Again back to Dashboard, Now Sync with stripe. Finally, refresh the page again. + +![](<../.gitbook/assets/1 (2).png>) diff --git a/TL--documentation-new/product-settings/deleting-an-entire-product.md b/TL--documentation-new/product-settings/deleting-an-entire-product.md new file mode 100644 index 0000000000000000000000000000000000000000..17e21fc44b8f31ea5dd403d86f15d990f1dd3d45 --- /dev/null +++ b/TL--documentation-new/product-settings/deleting-an-entire-product.md @@ -0,0 +1,13 @@ +# ๐Ÿ—‘ Deleting an entire product + +1. To remove a product, you must archive all the prices associated with the target product following the below guide. + +{% content-ref url="deleting-a-product-price.md" %} +[deleting-a-product-price.md](deleting-a-product-price.md) +{% endcontent-ref %} + +2\. Once all the prices are archived, you can archive the whole product in Stripe. + +3\. Once the product is archived in Stripe, you will need to re-sync the desired product in our Admin Dashboard. + +![](<../.gitbook/assets/image (3).png>) diff --git a/TL--documentation-new/product-settings/disabling-the-products-stock.md b/TL--documentation-new/product-settings/disabling-the-products-stock.md new file mode 100644 index 0000000000000000000000000000000000000000..1f7b14862af200ea3efe77e55ea44855e9d25566 --- /dev/null +++ b/TL--documentation-new/product-settings/disabling-the-products-stock.md @@ -0,0 +1,21 @@ +# ๐Ÿ“ฅ Disabling the product's stock + +{% hint style="info" %} +The residential purchases can be limited or even stopped. Follow the guide +{% endhint %} + +1. If you check the dashboard it can be purchased now. + +![](<../.gitbook/assets/1 (71) (3).png>) + +2\. Go to your admin dashboard then products and select the plan, Click on edit icon as shown below. + +![](<../.gitbook/assets/1 (72) (5).png>) + +3\. Turn off the red icon as shown below to disable the purchases. + +![](<../.gitbook/assets/1 (73) (4).png>) + +4\. Now refresh the dashboard page and it will be out of stock. + +![](<../.gitbook/assets/1 (74).png>) diff --git a/TL--documentation-new/product-settings/enabling-the-products-stock.md b/TL--documentation-new/product-settings/enabling-the-products-stock.md new file mode 100644 index 0000000000000000000000000000000000000000..8631d354b4c4d1382807e76ccf3c5b1c63d837f5 --- /dev/null +++ b/TL--documentation-new/product-settings/enabling-the-products-stock.md @@ -0,0 +1,21 @@ +# ๐Ÿ“ค Enabling the product's stock + +{% hint style="info" %} +To accept orders from your residential product follow the below steps. +{% endhint %} + +1. Now the purchases are out of stock,To start accepting orders follow the below steps. + +![](<../.gitbook/assets/1 (71) (6).png>) + +2\. Go to dashboard then products and edit by clicking the edit icon. + +![](<../.gitbook/assets/1 (72) (6).png>) + +3\. Turn on the red button as shown below so its active. + +![](<../.gitbook/assets/1 (73) (3).png>) + +4\. Now refresh the page and you can accept the orders. + +![](<../.gitbook/assets/1 (74) (2).png>) diff --git a/TL--documentation-new/product-settings/product-metadata.md b/TL--documentation-new/product-settings/product-metadata.md new file mode 100644 index 0000000000000000000000000000000000000000..9b11cf1ee5ffaec99d5e6d26771b002f5eedc067 --- /dev/null +++ b/TL--documentation-new/product-settings/product-metadata.md @@ -0,0 +1,93 @@ +# ๐Ÿ“Ž Product metadata + +{% hint style="warning" %} +Please ensure you copy and paste the metadata tags exactly as shown in our guides to avoid any mistakes. +{% endhint %} + +{% hint style="info" %} +The _**amount**_ metadata/parameter in the data center and accounts tab is what dictates the quantity to be delivered. It is especially useful when using the automatic delivery mode as it will deliver exactly the quantity specified. For example, if you are selling subnets that come in the size of 254 ISPs, you can stack these on top of each other and the automatic mode will auto deliver the correct subnets to the right person. +{% endhint %} + +## Residential Product + +{% content-ref url="../onboarding-guide/onboarding-a-residential-product.md" %} +[onboarding-a-residential-product.md](../onboarding-guide/onboarding-a-residential-product.md) +{% endcontent-ref %} + +| API | First metadata field | Second metadata field | Quantity metadata | +| ------------- | -------------------- | --------------------- | ----------------- | +| Oxylabs | torchlabs\_product | torchlabs\_elite | data\_gb | +| Private | torchlabs\_product | torchlabs\_premium | data\_gb | +| Packet Stream | torchlabs\_product | torchlabs\_basic | data\_gb | +| Smart Proxies | torchlabs\_product | torchlabs\_smart | data\_gb | +| IP Royal | torchlabs\_product | torchlabs\_iproyal | data\_gb | +| Brightdata | torchlabs\_product | torchlabs\_brightdata | data\_gb | +| More soon.. | | | | + +**Example:** + +This is an example of the packet stream product. First field input _**torchlabs\_product**_ (this tag helps us identify the products that you make for the proxy dashboard vs other products on your Stripe account), and the second field is _**torchlabs\_basic**_ which is used to identify the _Packetstream_ API + +![](<../.gitbook/assets/Screen Shot 2022-03-23 at 10.51.23 PM.png>) + +The next example is the quantity of the actual price section. In the below example, the customer will see a product on the dashboard for 15 GB of the Killer Basic plan for $140. We use the _**data\_gb** _ metadata tag to identify the quantity that is required to be delivered. If this tag is incorrect then they will not get any data delivered. In the field next to the _**data\_gb**_ we have the actual quantity in gigabytes, in this case 15 GB (only put the value and not the letters GB - again referring to this example, it will be just 15) + +![](<../.gitbook/assets/Screen Shot 2022-03-23 at 11.01.07 PM.png>) + +## Data center Product + +{% content-ref url="../data-center-and-accounts/adding-data-center-products.md" %} +[adding-data-center-products.md](../data-center-and-accounts/adding-data-center-products.md) +{% endcontent-ref %} + +| Product | First metadata field | Second metadata field | Quantity metada | +| --------- | -------------------- | ------------------------------ | --------------- | +| Product 1 | torchlabs\_product | torchlabs\_datacenter\_daily | amount | +| Product 2 | torchlabs\_product | torchlabs\_datacenter\_weekly | amount | +| Product 3 | torchlabs\_product | torchlabs\_datacenter\_monthly | amount | +| Product 4 | torchlabs\_product | torchlabs\_datacenter\_extra1 | amount | +| Product 5 | torchlabs\_product | torchlabs\_datacenter\_extra2 | amount | +| Product 6 | torchlabs\_product | torchlabs\_datacenter\_extra3 | amount | +| Product 7 | torchlabs\_product | torchlabs\_datacenter\_extra4 | amount | +| Product 8 | torchlabs\_product | torchlabs\_datacenter\_extra5 | amount | +| Product 9 | torchlabs\_product | torchlabs\_datacenter\_extra6 | amount | + +**Example** + +This is an example of Data center product. First field input _**torchlabs\_product**_ (this tag helps us identify the products that you make for the proxy dashboard vs other products on your Stripe account), and the second field is _**torchlabs\_weekly**_ which is used to identify a unique product. + +{% hint style="warning" %} +There is some confusion regarding the terminology behind daily,weekly, monthly on the metadata - These actually mean nothing. It is only used to differentiate between all the data center products. They can be used interchangeably as well. For example, if you are selling Yeezysupply daily proxies, you can use any of the 3 metadata tags +{% endhint %} + +![](<../.gitbook/assets/Screen Shot 2022-03-23 at 11.01.57 PM (1).png>) + +The next example is the quantity of the actual price section. In the below example, the customer will see a product on the dashboard for 100 Killer ISPs for $300. We use the _**amount** _ metadata tag to identify the quantity that is required to be delivered. If this tag is incorrect then they will not get any data delivered. In the field next to the _**amount**_ we have the actual quantity in units, in this case, 100 ISPs (only put the value and not the letters ISP - again referring to this example, it will be just 100) + +![](<../.gitbook/assets/Screen Shot 2022-03-23 at 11.05.49 PM.png>) + +## Account Product + +{% hint style="info" %} +With the Accounts Product, you can make up to 9 unique products (if you need more let us know!) and unlike data center, the metadata is all the same for all the products...we use some magic behind the scene to make it all work! +{% endhint %} + +{% content-ref url="../data-center-and-accounts/adding-account-products.md" %} +[adding-account-products.md](../data-center-and-accounts/adding-account-products.md) +{% endcontent-ref %} + +| Product | First metadata field | Second metadata field | Quantity metadata | +| ------------- | -------------------- | --------------------- | ----------------- | +| Product 1 - 9 | torchlabs\_product | torchlabs\_accounts | amount | + +You can repeat the above metadata for up to 9 products. + +**Example:** + +This is an example of an Account product. First field input _**torchlabs\_product**_ (this tag helps us identify the products that you make for the proxy dashboard vs other products on your Stripe account), and the second field is _**torchlabs\_accounts**_ which is used to identify an accounts product. + +![](<../.gitbook/assets/Screen Shot 2022-03-23 at 11.27.43 PM.png>) + +The next example is the quantity of the actual price section. In the below example, we are using the accounts tab to sell ISP subnets but you can sell whatever you want such as Gmails and FLX accounts. In our example, the customer will see a product on the dashboard for 254 Killer ISPs for $400. We use the _**amount** _ metadata tag to identify the quantity that is required to be delivered. If this tag is incorrect then they will not get any data delivered. In the field next to the _**amount**_ we have the actual quantity in units, in this case, 254 ISPs (only put the value and not the letters ISP - again referring to this example, it will be just 254) - Again you can do this with anything not just ISPs. + +![](<../.gitbook/assets/Screen Shot 2022-03-23 at 11.27.53 PM.png>) diff --git a/TL--documentation-new/product-settings/reorder-your-products.md b/TL--documentation-new/product-settings/reorder-your-products.md new file mode 100644 index 0000000000000000000000000000000000000000..37a4d206d98c1a1cee33a564ae0a28d638450c04 --- /dev/null +++ b/TL--documentation-new/product-settings/reorder-your-products.md @@ -0,0 +1,17 @@ +# ๐Ÿชœ Reorder your products + +{% hint style="info" %} +In order to change the position of your plans in the dashboard follow the guide. +{% endhint %} + +1. The dashboard plans position can be changed. + +![](<../.gitbook/assets/1 (71) (4).png>) + +2\. Go to Admin Dashboard products section, The plans can be moved up and down. Hover it as you wish and it will get auto saved. + +![](<../.gitbook/assets/1 (72) (7).png>) + +3\. Finally reload the dashbaord the changes will be appeared. + +![](<../.gitbook/assets/1 (73) (2).png>) diff --git a/TL--documentation-new/proxy-masking/loadbalancer-management.md b/TL--documentation-new/proxy-masking/loadbalancer-management.md new file mode 100644 index 0000000000000000000000000000000000000000..3ba8f63c8bcd99fd8b2cfa63d6e1cd59406726ad --- /dev/null +++ b/TL--documentation-new/proxy-masking/loadbalancer-management.md @@ -0,0 +1,57 @@ +# โš– Loadbalancer management + +{% hint style="info" %} +This guide will go over on how to properly scale and manage your load balancer to ensure you have the optimal performance on your proxies. Managing the load balancer is very important as this determines how much traffic you can accept. If your load balancer is not set up for the right amount of traffic (too small) then all the proxies will fail. Therefore, it is essential to follow the below recommendations. +{% endhint %} + +{% hint style="danger" %} +DO NOT CHANGE ANYTHING IN THE SERVER/DROPLET SECTION. Changing anything here will cause the masking to not work and all your proxies will fail to connect. +{% endhint %} + +Based on your setup, your DO account should look something like the below image: + +![](../.gitbook/assets/Screen\_Shot\_2022-02-23\_at\_10.22.07\_AM.png) + +The **LOAD BALANCERS** is where all your load balancers exist + +The **DROPTLETS** is where all your servers exist + + + +### What is a load balancer? + +_Load balancing_ refers to efficiently distributing incoming network traffic across a group of backend servers, also known as a server farm or server pool. + +### What is a server (DO refers to servers as droplet)? + +In computing, a server is a piece of computer hardware or software that provides functionality for other programs or devices, called "clients". + +### Managing your load balancer + +Our special masking script is installed on your servers. This script routes the traffic to the proxy domain via the server acting as a middle man. However, all the initial traffic comes to one main point which is the load balancers. Then the load balancer distributes this traffic to one or more connected servers. + +![](<../.gitbook/assets/image (7).png>) + +A load balancer on DO can handle 10,000 simultaneous connections and 10,000 connections per second. What this means is that each connection is one proxy connection coming from a user. So based on how many users you have and how much demand you anticipate for a drop you need to increase the number of load balancer nodes. Each extra node gives you an additional 10,000 simultaneous connections. + +For example, you have one user who is running 2000 tasks. These 2000 tasks would equate to basically 2000 simultaneous connections. You need to determine the demand for each drop and the number of running users and scale the load balancer accordingly. + +You are charged an additional cost for each node by DO, however, you can scale back down after the drop to avoid incurring large costs. By scaling up and down manually you can avoid getting charged a lot of money and you can still have a very smooth drop. + + + +### Resize your load balancer + +1. Click on your load balancer + +2\. Go to settings + +![](<../.gitbook/assets/Screen Shot 2022-03-20 at 3.44.21 PM.png>) + +3\. Go to scaling configuration and click resize + +![](<../.gitbook/assets/Screen Shot 2022-03-20 at 3.44.59 PM.png>) + +4\. From here you can select the size of nodes you want. You can increase or decrease the number of nodes. + +![](<../.gitbook/assets/Screen Shot 2022-03-20 at 3.45.33 PM (1).png>) diff --git a/TL--documentation-new/proxy-masking/proxy-masking-guide.md b/TL--documentation-new/proxy-masking/proxy-masking-guide.md new file mode 100644 index 0000000000000000000000000000000000000000..38997cbd35a5dc3e33ca05db78f8cc730ec62722 --- /dev/null +++ b/TL--documentation-new/proxy-masking/proxy-masking-guide.md @@ -0,0 +1,21 @@ +# ๐Ÿ˜ท Proxy Masking Guide + +1. Please click this link: [https://m.do.co/c/b45a1eda4839](https://m.do.co/c/b45a1eda4839) + +{% embed url="https://m.do.co/c/b45a1eda4839" %} + +{% hint style="success" %} +By using our link you get 100$ free credits for hosting which should cover your costs for about 2-3 months! +{% endhint %} + +2\. Please follow the instructions and make an account on Digital Ocean using the above link + +3\. Go to your profile and click create Invite new team members + +
+ +4\. Next add our email as a team member invite: `torchlabsxyz@gmail.com` + +
+ +`5.` That's it! everything should be set up in 24-36 hours! diff --git a/TL--documentation-new/residential-products/adding-residential-products.md b/TL--documentation-new/residential-products/adding-residential-products.md new file mode 100644 index 0000000000000000000000000000000000000000..71b956c04490c37a150951f696c9dad273b06927 --- /dev/null +++ b/TL--documentation-new/residential-products/adding-residential-products.md @@ -0,0 +1,83 @@ +# โœ… Adding residential products + +{% hint style="info" %} +This guide will help to set up residential products for your dashboard. +{% endhint %} + +{% content-ref url="../product-settings/product-metadata.md" %} +[product-metadata.md](../product-settings/product-metadata.md) +{% endcontent-ref %} + +{% embed url="https://youtu.be/ugkvgPD_kfg" %} + +1\. Firstly, Log in to the Stripe Account. + +![](<../.gitbook/assets/Untitled design (1) (3).png>) + +2\. Right Side of the Stripe Dashboard find Products and click that. + +![](<../.gitbook/assets/Untitled design (2) (10).png>) + +3\. Next Add Products + +![](<../.gitbook/assets/Untitled design (3) (10).png>) + +4\. Then name your product + +![](<../.gitbook/assets/Untitled design (4) (1).png>) + +5\. Also set the price for your product. + +![](<../.gitbook/assets/Untitled design (5) (6).png>) + +6\. Click "One Time" below Price. + +![](<../.gitbook/assets/Untitled design (6) (2).png>) + +7\. To add another product, Repeat the process. + +![](<../.gitbook/assets/Untitled design (7) (2).png>) + +8\. After adding the products, View Additional Options. + +![](<../.gitbook/assets/Untitled design (8) (6).png>) + +9\. Then add Metadata for your desired residential provider using our meta data guide guide below. + +{% content-ref url="../product-settings/product-metadata.md" %} +[product-metadata.md](../product-settings/product-metadata.md) +{% endcontent-ref %} + +![](<../.gitbook/assets/Untitled design (2) (1).png>) + +10\. Here you can view all the prices created, And click on a price. + +![](<../.gitbook/assets/Untitled design (1) (8).png>) + + + +11\. To add bandwidth limit Click Edit MetaData. In the first field add "data\_gb" followed but your desired number of GB for that price and save. And repeat the same for other prices as well. + + + +{% hint style="info" %} +In this example, there will be 1 gb being delivered to the customer. +{% endhint %} + +![](<../.gitbook/assets/Untitled design (11) (7).png>) + +12\. Now go-to products and now we are done with our first product. We do not recommend making more than 6 prices per product. + +![](<../.gitbook/assets/Untitled design (12) (2).png>) + +13\. Then go to dashboard and products section and choose your selected plan and edit it. + +![](<../.gitbook/assets/1 (72) (1).png>) + +14\. Then click Sync with Stripe to sync all the prices. + +![](<../.gitbook/assets/1 (67) (3).png>) + +15\. Once the sync is completed, you should see the number of GB next to the prices you set. Repeat this process if you are using multiple API's. + +![](<../.gitbook/assets/1 (68) (2).png>) diff --git a/TL--documentation-new/residential-products/residential-pools.md b/TL--documentation-new/residential-products/residential-pools.md new file mode 100644 index 0000000000000000000000000000000000000000..54f32abf55aaec4d93402cfadaf646bcd5da3773 --- /dev/null +++ b/TL--documentation-new/residential-products/residential-pools.md @@ -0,0 +1,63 @@ +--- +description: We have added special residential pools based on select countries. +--- + +# ๐ŸŠโ™‚ Residential pools + +{% hint style="success" %} +These pools can be found on the customer dashboard in the country drop down under a โ€œSpecialโ€ category. +{% endhint %} + +Footsites US - \[US] + +Footsites CA- \[CA] + +Footsites EU- \[UK, Germany,France - Keep in mind that the countries are different in each of our providers so country codes change between them] + +Footsites AU- \[Australia] + +Footsites SG- \[singapore, China] + +Footsites MY- \[Malaysia, China] + +Asia - \[Japan,China] + +Yeezysupply - \[US] + +Supreme US - \[US] + +Supreme EU - \[UK, Germany,France - Keep in mind that the countries are different in each of our providers so country codes change between them] + +Supreme JP - \[Japan] + +Nike US - \[US] + +Nike EU - \[UK, Germany,France - Keep in mind that the countries are different in each of our providers so country codes change between them] + +Nike MY - \[Malaysia, China, Singapore] + +Mesh - \[UK, Germany,France] + +courir - \[UK, Germany,France ] + +EU 1 - \[UK, Germany,France ] + +EU 2 - \[Spain,Sweden, Russia, France,Ukraine] + +EU 3 - \[Italy, Germany,France] + +EU 4 - \[Turkey, Netherlands,Romania] + +EU 5 - \[Greece, Bulgaria,Portugal,Ireland,lithuania] + +EU SC - (Iceland, Norway, Sweden, Finland, and Denmark) + +EU W - (France, Belgium, the Netherlands, Luxembourg, and Monaco) + +EU S - (Portugal, Spain, Italy); + +EU C -(Germany, Switzerland, Austria, Poland, the Czech Republic, Slovakia, and Hungary) + +EU S - (Slovenia, Croatia, Bosnia and Herzegovina, Serbia, Macedonia, Romania, Bulgaria, Greece, and Turkey + +EU E Europe (Estonia, Latvia, Lithuania, Belarus, Ukraine, Moldova, Russia, Georgia, Armenia, and Azerbaijan) diff --git a/TL--documentation-new/residential-products/residential-provider-information.md b/TL--documentation-new/residential-products/residential-provider-information.md new file mode 100644 index 0000000000000000000000000000000000000000..207ce80ec00fe34aab5e5406e5791e9c10990304 --- /dev/null +++ b/TL--documentation-new/residential-products/residential-provider-information.md @@ -0,0 +1,59 @@ +--- +description: >- + We currently support all major APIs in the market such as Oxylab, Private , + Packetstream , Brightdata, IProyal & Smart proxies. +--- + +# โ„น Residential Provider Information + +
+ +## **Oxylabs Residential Proxies** + +* Unlimited concurrent sessions. +* Avg. 0.6s proxy speed. +* Continuous proxy rotation for avg. 99.2% success rates. +* Country, city, and state-level targeting with no extra cost. +* 100M+ Residential Proxy pool. +* Supports all major sites. + +## **Smart Residential Proxies** + +* 40M+ real device IPs. +* 195+ locations. +* 24/7 instant epic support. +* Full anonymity and security. +* Unlimited connections and threads. +* Advanced rotation. +* Supports all major sites except for the following [blacklisted sites](https://smartproxy.com/questions/do-you-have-any-blocked-sites). + +## **Brightdata Residential Proxies** + +* Target any country, city, carrier & ASN. +* 99.99% uptime - extremely stable. +* 72+ million ethically-sourced IPs. +* Supports all major sneaker sites. Here is a full [site list](https://supreme-conga-5d4.notion.site/Bright-data-Site-list-bc755d0dcd21468e95750c87de7c5b8a). + +## **IProyal Residential Proxies** + +* Auto-Rotate - every 1, 10, or 30 minutes. +* 3 Million IPs. +* Sticky proxy session. +* Unlimited concurrent sessions. +* 180+ countries. +* Supports all major sites. + +## **Packetstream Residential Proxies** + +* 7+ Million Residential IPs. +* 180+ countries. +* 99% Uptime. +* 0 Restrictions +* Supports all major sites. + +## **Private Residential Proxies** + +* A pool of 8M+ IPs to help you crawl freely +* 99% uptime with a mix of ISP, mobile proxies and real residential proxies. +* 180+ countries. +* Supports all major sites. diff --git a/TL--documentation-new/residential-products/top-up-data-manually.md b/TL--documentation-new/residential-products/top-up-data-manually.md new file mode 100644 index 0000000000000000000000000000000000000000..6649ed572dc9de7536427698c80ff9632a3f5815 --- /dev/null +++ b/TL--documentation-new/residential-products/top-up-data-manually.md @@ -0,0 +1,21 @@ +# ๐Ÿ‘† Top up data manually + +{% hint style="info" %} +This guide will show you how to update data's manually to your user's account. +{% endhint %} + +1. Torch Lab users have a choice of **three data** plans from which to pick. + +![](<../.gitbook/assets/Untitled design (12).png>) + +2\. The data can be purchased in the marked area just by increasing and decreasing through the line. The price per GB and Total price for the purchase will appear in two boxes below and Simply click **BUY.** + +![](<../.gitbook/assets/Untitled design (1).png>) + +3\. Finally checkout will be arrived, Here are the payment card details to be filled in and click **PAY.** + +![](<../.gitbook/assets/Untitled design (22) (1).png>) + +4\. The balance GB will be always displaying here. + +![](<../.gitbook/assets/Untitled design (7).png>) diff --git a/TL--documentation-new/residential-products/updating-users-data-balance.md b/TL--documentation-new/residential-products/updating-users-data-balance.md new file mode 100644 index 0000000000000000000000000000000000000000..f4e08f80de275eb325263e17334e0759b34cd6d1 --- /dev/null +++ b/TL--documentation-new/residential-products/updating-users-data-balance.md @@ -0,0 +1,28 @@ +# ๐Ÿ’ป Updating user's data balance + +{% hint style="info" %} +This guide will show you how to top up your user's data balance. +{% endhint %} + +โ€‹1. In the _**Users**_ tab, find your desired user. + +![](<../.gitbook/assets/image (16).png>) + +2.Click on the user. + +3\. Next, you will get a pop up where you can select the data plan by clicking the Dropdown. + +![](<../.gitbook/assets/image (1).png>) + +4\. In the Data GB box, you can add the desired amount of data you want to add on top of the users existing balance. + +{% hint style="info" %} +Enter Positive values to add data and negative values to remove data + +EG: 5 -> this will add the user 5 GB to their existing balance + +EG: -2 -> this will deduct the user 2 GB from their existing balance +{% endhint %} + +![](<../.gitbook/assets/image (15).png>) + diff --git a/TL--documentation-new/residential-products/user-management.md b/TL--documentation-new/residential-products/user-management.md new file mode 100644 index 0000000000000000000000000000000000000000..587fd8991f2fe41f39e0f12fc8f06ca11699890c --- /dev/null +++ b/TL--documentation-new/residential-products/user-management.md @@ -0,0 +1,20 @@ +# ๐Ÿ‘ฎโ™€ User management + +{% hint style="info" %} +This guide will help you to keep track of your dashboard logged ins. +{% endhint %} + +1. In the _**Users**_ tab, the dashboard will display all users who have logged into the proxy dashboard. The dashboard will display the users' Discord ID, Avatar, Discord Tag, Email Address and the date first logged in. + +![](<../.gitbook/assets/Untitled design (4) (12).png>) + +2\. You can also search for a user by their Discord ID. + +{% hint style="info" %} +How to get Discord ID: [https://youtu.be/VTgVsQ0gwKM](https://youtu.be/VTgVsQ0gwKM) +{% endhint %} + +Click the user to top manually. + +![](<../.gitbook/assets/Untitled design (5) (2).png>) + diff --git a/TL--documentation-new/residential-products/view-users-current-balance.md b/TL--documentation-new/residential-products/view-users-current-balance.md new file mode 100644 index 0000000000000000000000000000000000000000..f4ff45967ac5bf3ba04c9933e81d5e7c2146b6d5 --- /dev/null +++ b/TL--documentation-new/residential-products/view-users-current-balance.md @@ -0,0 +1,17 @@ +# โณ View users current balance + +{% hint style="info" %} +This guide will help to keep track of your user's current balance for each of the user's plans. +{% endhint %} + +โ€‹1. In the _**Users**_ tab, find your desired user. + +![](../.gitbook/assets/3.jpg) + +2\. When you click on the user, after a few seconds once the pop up appears, it will contain the users existing balance for each of their plans. There is a button called "Show usage" which will lead you to get the usage of data of each user. + +![](../.gitbook/assets/1.jpg) + +Every 10 seconds usage could be refreshed and get the updated usage of each user. + +![](../.gitbook/assets/2.jpg)